A1 ratingsPrinceton/Stanford NLPSWE-agent

SWE-agent
Princeton/Stanford NLP · agent · Any industry
CGrade
41Score
±795% range
#602Rank of 1134
0%From fleets
FR-CAT-00851Catalog no.
The six pillars
Each bar is the score; the bracket is its 95% range.
Can you see what it costs?
Only through a gateway you run · prices published
Desk research 60 · counts for 25% · A cost API you can call scores highest; an admin console or cloud billing export next; a card statement or emailed invoice is all some products leave you. Published prices add to it.
Can you see how much it's used?
No usage API found
Desk research 50 · counts for 15% · A usage API (tokens, seats, credits, conversations) a buyer can read.
Can you tie cost to one agent?
Nothing a buyer can read
Desk research 0 · counts for 15% · Exact (one key or project per agent) beats by-project, by-workspace or by-user.
Can an agent on it report out?
SDK · Self-run Python research agent with your own model key; meter at the provider or a gateway.
Desk research 70 · counts for 15% · A remote MCP connector scores highest, then a local MCP server, an SDK, an API or a workflow step; copy-and-paste lowest. Any open standard counts, not just FleetRegistry.
Can you control spend and access?
Spend cap: Hard cap · Per-agent keys: One shared key · Audit log: None · Revoke: None · SSO: None
Desk research 30 · counts for 20% · Hard spend caps (30%), scoped per-agent keys (25%), an audit log you can read by API (20%), revoking by API (15%), SSO with SCIM (10%).
Does it work on small plans?
Small plans don't get the data
Desk research 0 · counts for 10% · Whether the plan a person or small business buys gets the cost and usage data at all.
Where the evidence comes from
Independent fleets0%Desk research80%Neutral starting point20%
Once three independent fleets report on a pillar, desk research counts for at most a third of it. FleetRegistry's own fleets never count.
Controls on record
Spend capHard cap
Per-agent keysOne shared key
Audit logNone
RevokeNone
SSONone
PricesPublished
Free open-source research agents with no vendor-side controls. The only built-in guard is a local per-run cost cap (mini-swe-agent cost_limit, SWE-agent per_instance/total cost limits) plus step limits; keys come from the user's own env.
History
11-12 C 4111-13 C 4111-14 C 4111-15 C 4111-16 C 4111-17 C 4111-18 C 4111-19 C 41
Rated since 2026-10-02. Published grades are sealed daily into the transparency log (N4.4). Grade held since 2026-10-02.Run agents on SWE-agent?
Give each one a permanent number, a named person who answers for it, and a record of what it can touch and what it costs. Free.