A1 ratingsAnysphere (SpaceX/xAI)Cursor Background/Cloud Agents

Cursor Background/Cloud Agents

Anysphere (SpaceX/xAI) · agent · Any industry
B
BGrade
68Score
±1195% range
#101Rank of 1134
0%From fleets
FR-CAT-00587Catalog no.

The six pillars

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

Can you see what it costs?

Vendor cost API (Cursor Admin API (usage data and spending; Enterprise teams)) · prices published
86±27
Desk research 100 · 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?

Cursor Analytics API (team usage, active users, model adoption; Enterprise)
86±27
Desk research 100 · counts for 15% · A usage API (tokens, seats, credits, conversations) a buyer can read.

Can you tie cost to one agent?

By user
50±27
Desk research 50 · 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 · Cloud Agents API (all plans, beta) plus TypeScript/Python SDKs; supports MCP
64±27
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: Not scoped · Audit log: By API · Revoke: Console only · SSO: SSO + SCIM
75±27
Desk research 86 · 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
14±27
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 research71%Neutral starting point29%

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 scoped
Audit logBy API
RevokeConsole only
SSOSSO + SCIM
PricesPublished

Price changes: ToS 4.2: fees may change with advance notice via UI, email or other reasonable means; no fixed period.

Spend limits are a hard stop on paid additional usage (brief overshoot possible). On The X Subscription (new customers, Oct 2026) on-demand limits are replaced by top-ups and a monthly additional usage limit; Teams set one team limit (admins only); Enterprise adds member/group overrides via Admin API. SCIM, audit logs with SIEM streaming and service accounts are Enterprise-only; Admin keys carry admin:* scope, service-account keys have no documented per-key scopes.

History

11-12 B 6811-13 B 6811-14 B 6811-15 B 6811-16 B 6811-17 B 6811-18 B 6811-19 B 68
Rated since 2026-10-02. Published grades are sealed daily into the transparency log (N4.4). Grade held since 2026-10-02.

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
Vendor cost API Declared
medium confidence
2026-10-20
1 earlier
[1][2][3] Correct
Prices published
Cost
Yes Declared
medium confidence
2026-10-20
1 earlier
[1][2][3][4] Correct
Usage API
Usage
Cursor Analytics API (team usage, active users, model adoption; Enterprise) Declared
medium confidence
2026-10-20
1 earlier
[1][2][3] Correct
Cost per agent
Per agent
By user Declared
medium confidence
2026-10-20
1 earlier
[1][2][3] Correct
How an agent reports out
Reports out
SDK Declared
medium confidence
2026-10-20
1 earlier
[1][2][3] Correct
Per-agent keys
Controls
Not scoped Declared
medium confidence
2026-10-20
1 earlier
[1][2][3][4] Correct
Audit log
Controls
By API Declared
medium confidence
2026-10-20
1 earlier
[1][2][3][4] Correct
Revoke access
Controls
Console only Declared
medium confidence
2026-10-20
1 earlier
[1][2][3][4] Correct
Spend cap
Controls
Hard cap Declared
medium confidence
2026-10-20
1 earlier
[1][2][3][4] Correct
SSO
Controls
SSO + SCIM Declared
medium confidence
2026-10-20
2 earlier
[1][2][3][4] Correct
Small plans get the data
Small plans
No Declared
medium confidence
2026-10-20
1 earlier
[1][2][3] Correct

Prices · X Subscription (new customers): Plus $8 (India), Premium $30, Super $100, Ultra $200/mo; Teams $30 or $100/user; third-party models at API list price. Legacy: Pro $20 / Pro+ $70 / Ultra $400 usage pools; Teams $40/user. Cloud agents at model API rates; VM compute 'coming'

Notes · New customers now start on 'The X Subscription' (Oct 2026; billing at grok.com/dashboard/billing): one weekly usage pool shared with Grok, third-party models billed at API list price from prepaid credit, extra usage via top-ups with a monthly additional usage limit. Legacy Pro/Pro+/Ultra/Teams continue unless switched. Cloud Agents charged at model API rates; VM compute still unpriced. Admin API (usage/spend, admin:* key) and Analytics API remain Enterprise-only; Cloud Agents API all plans (beta). Default rate limit 20 req/min; usage endpoints aggregate hourly.

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

Corrections

1 awaiting review. Accepted corrections are published in the corrections register with an FR-C number.

Run agents on Cursor Background/Cloud Agents?

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.