A1 ratingsReplitReplit Missions

Replit Missions

Replit · agent · Any industry Provisional
C
CGrade
45Score
±1895% range
≈#496Rank of 1136
0%From fleets
FR-CAT-01611Catalog no.
Provisional: the range is wide because some facts are thin or not yet known. It narrows as research and fleets fill in.

The six pillars

Each bar is the score; the bracket is its 95% range.

Can you see what it costs?

Nothing a buyer can read · prices on request only
25±38
Desk research 0 · 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
25±38
Desk research 0 · counts for 15% · A usage API (tokens, seats, credits, conversations) a buyer can read.

Can you tie cost to one agent?

partial
50±59
Not known yet. Sits at a neutral 50 with a wide range until facts arrive · 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?

50±59
Not known yet. Sits at a neutral 50 with a wide range until facts arrive · 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
86±27
Desk research 100 · 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
25±38
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 research39%Neutral starting point61%

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 keysNot known
Audit logNot known
RevokeNot known
SSONot known
PricesOn request

Each mission has a USD spending limit; it pauses when the limit is reached and any increase needs the user's approval. Users choose which decisions need approval and which connectors the mission can access.

History

Not saved yet. Published grades are sealed daily into the transparency log (N4.4). Grade held since 2026-11-19.

Every fact, with its rung and source

Each fact stands on its own source and its own rung of the evidence ladder (Rule N2.1). Verified Observed Declared Inferred. The weakest fact in a pillar sets its weight.

FactValueRungCheckedSources
How a buyer sees cost
Cost
None found Inferred 2026-11-19
1 earlier
[1][2] Correct
Prices published
Cost
No Declared
medium confidence
2026-11-19 [1] Correct
Usage API
Usage
None found Inferred 2026-11-19 [1][2] Correct
Cost per agent
Per agent
partial Inferred 2026-11-19 [1][2] Correct
Spend cap
Controls
Hard cap Declared
medium confidence
2026-11-19 [1] Correct
Small plans get the data
Small plans
No Inferred 2026-11-19 [1][2] Correct

Prices · No per-mission price published; each mission has a user-set maximum budget and work (including messages sent during the mission) counts toward it

Notes · Launched Nov 17 2026. Missions page FAQ says you set a maximum budget per mission and work performed counts toward it; it does not say which plans include Missions. Per-mission spend is shown by step in the UI; no Missions-specific usage or cost API is documented.

Scored with the rubric for Agents and agent platforms (Rule N7.1). Each pillar blends a neutral 50, desk facts weighted by rung, and independent fleets. A1 is 85+ with fleet proof, A 70, B 55, C 40, D 25, E below. Part N of the Rules

Run agents on Replit Missions?

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.