A1 ratingsA2EA2E Developer API

A2E Developer API

A2E · platform · Any industry Provisional
C
CGrade
48Score
±1695% range
≈#432Rank of 1134
0%From fleets
FR-CAT-01598Catalog 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?

Only your card statement · prices published
43±27
Desk research 40 · 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
14±27
Desk research 0 · counts for 15% · A usage API (tokens, seats, credits, conversations) a buyer can read.

Can you tie cost to one agent?

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?

Per-agent keys: Not scoped
57±27
Desk research 60 · 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 get the data
86±27
Desk research 100 · 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 research50%Neutral starting point50%

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 capNot known
Per-agent keysNot scoped
Audit logNot known
RevokeNot known
SSONot known
PricesPublished

Pricing FAQ says developers create an API token once on an eligible plan; no scoping, revocation, SSO or audit-log documentation found.

History

11-17 C 4811-18 C 4811-19 C 48
Rated since 2026-11-17. Published grades are sealed daily into the transparency log (N4.4). Grade held since 2026-11-16.

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
Only your card statement Declared
medium confidence
2026-11-16 [1][2][3][4] Correct
Prices published
Cost
Yes Declared
medium confidence
2026-11-16 [1][2] Correct
Usage API
Usage
None found Declared
medium confidence
2026-11-16 [1][2][3][4] Correct
Per-agent keys
Controls
Not scoped Declared
medium confidence
2026-11-16 [1][2] Correct
Small plans get the data
Small plans
Yes Declared
medium confidence
2026-11-16 [1][2][3][4] Correct

Prices · API access requires a Pro ($14.90) or Ultra plan; usage drawn from the same prepaid credits (e.g. lipsync video 1 credit/s; streaming avatar 1 coin per 5 s); volume pricing, dedicated servers and on-premise by arrangement.

Notes · Billed by prepaid credits under the same account plans; pricing page lists by-usage, dedicated server and on-premise payment methods. No billing or usage endpoint found in the docs read.

Scored with the rubric for Platforms and APIs (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 A2E Developer API?

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.