A1 ratingsOpenAIOpenAI API

OpenAI API

OpenAI · platform · Any industry
A
AGrade
76Score
±1195% range
#18Rank of 1134
0%From fleets
FR-CAT-01215Catalog no.

The six pillars

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

Can you see what it costs?

Vendor cost API (Costs API GET /v1/organization/costs) · prices published
90±17
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 API GET /v1/organization/usage/completions (and other modalities)
90±17
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
90±17
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?

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 · Per-agent keys: Scoped · Audit log: By API · Revoke: By API · SSO: SSO + SCIM
90±17
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
10±17
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 research68%Neutral starting point32%

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 keysScoped
Audit logBy API
RevokeBy API
SSOSSO + SCIM
PricesPublished

Price changes: Services Agreement: pricing-page changes take effect 14 days after posting; material agreement changes get at least 30 days' notice.

API platform: org/project monthly spend limits enforce a hard stop (429 organization_/project_spend_limit_exceeded) only when 'Enforce a hard limit' is on; enforcement is not instantaneous so spend can slightly exceed the limit; spend alerts alone do not cap. Project service accounts and Restricted/Read-only keys with per-endpoint scopes; per-project model allow-lists and rate limits. Admin API lists/deletes project API keys; Audit Logs API (must be enabled, key needs Audit Logs read scope). SCIM for API orgs on Custom/Unlimited billing plans (configurable independently of SSO).

History

11-11 A 7611-12 A 7611-13 A 7611-14 A 7611-15 A 7611-16 A 7611-17 A 7611-18 A 76
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
high confidence
2026-10-25
1 earlier
[1][2] Correct
Prices published
Cost
Yes Verified 2026-11-16
2 earlier
[1][2][3][4] Correct
Usage API
Usage
Usage API GET /v1/organization/usage/completions (and other modalities) Declared
high confidence
2026-10-25
1 earlier
[1][2] Correct
Cost per agent
Per agent
Exact, per key or project Declared
high confidence
2026-10-25
1 earlier
[1][2] Correct
Per-agent keys
Controls
Scoped Declared
high confidence
2026-10-25
1 earlier
[1][2][3][4] Correct
Audit log
Controls
By API Verified 2026-11-02
2 earlier
[1][2][3][4] Correct
Revoke access
Controls
By API Declared
high confidence
2026-10-25
1 earlier
[1][2][3][4] Correct
Spend cap
Controls
Hard cap Declared
high confidence
2026-10-25
1 earlier
[1][2][3][4] Correct
SSO
Controls
SSO + SCIM Declared
high confidence
2026-10-25
1 earlier
[1][2][3][4] Correct
Small plans get the data
Small plans
No Declared
high confidence
2026-10-25
1 earlier
[1][2] Correct

Prices · Per-1M-token: GPT-6-Astra $10 in / $50 out; GPT-6-Luna $0.10 in / $0.50 out (short context); web search $10/1k calls; file storage $0.10/GB-day. Batch/Flex/Priority variants.

Notes · Group by api_key_id or project for per-agent attribution; Costs API is 1d-only, Usage API 1m/1h/1d; both need an Admin API key. Pricing page today: Priority processing was renamed 'Fast' mode on July 30, 2026 (the 'Priority' wording in list_prices refers to it); regional processing/FedRAMP carry a 10% uplift; OpenAI is winding down its fine-tuning platform; billing for gpt-rosalind-research began Oct 5, 2026. Third-party sources (community post, Brex charge finder) dropped; card descriptor not re-verified.

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 OpenAI 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.