A1 ratingsNEAR AINEAR AI Cloud

NEAR AI Cloud
NEAR AI · platform · Any industry
AGrade
74Score
±1395% range
≈#29Rank of 1134
0%From fleets
FR-CAT-01583Catalog no.
The six pillars
Each bar is the score; the bracket is its 95% range.
Can you see what it costs?
Vendor cost API (GET /v1/organizations/{org}/usage/export and /usage/summary (read-only reporting token, nano-USD, by workspace, API key, model); POST /v1/billing/costs per inference-id) · prices published
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?
Usage Reporting API; per-API-key usage history endpoint
Desk research 100 · counts for 15% · A usage API (tokens, seats, credits, conversations) a buyer can read.
Can you tie cost to one agent?
Exact, per key or project
Desk research 100 · 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?
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: Scoped · Revoke: By API
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
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 research64%Neutral starting point36%
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 keysScoped
Audit logNot known
RevokeBy API
SSONot known
PricesPublished
API keys are created per workspace, can expire, and carry an optional per-key spend_limit set via API; docs do not say whether hitting the limit blocks requests, so spend_cap is left unset. Org roles/members via API. No SSO or audit-log documentation found. Nov 8, 2026 SGLang RCE breach exposed two customers' keys in logs (revoked).
History
11-14 A 7411-15 A 7411-16 A 7411-17 A 7411-18 A 7411-19 A 74
Rated since 2026-11-14. Published grades are sealed daily into the transparency log (N4.4). Grade held since 2026-11-13.Run agents on NEAR AI Cloud?
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.