THE METHODOLOGY DEPARTMENT · RFC · FROZEN 2026-08-27
AI PROVIDER COST TRANSPARENCY INDEX
10 providers scored against 25 binary criteria — can a customer know what they will be charged, and see where the money went? Every score cites primary evidence, dated. Read the full methodology.
| Provider | Met | Not met | Not verifiable | Reply |
|---|---|---|---|---|
| Azure OpenAI | 23 | 0 | 2 | No reply |
| AWS Bedrock | 22 | 2 | 1 | No reply |
| 20 | 3 | 2 | No reply | |
| xAI | 20 | 0 | 5 | No reply |
| OpenAI | 18 | 5 | 2 | Replied |
| Anthropic | 17 | 4 | 4 | No reply |
| DeepSeek | 15 | 2 | 8 | No reply |
| OpenRouter | 15 | 8 | 2 | No reply |
| Mistral AI | 12 | 3 | 10 | No reply |
| Cohere | 9 | 2 | 14 | No reply |
BY BLOCK
Pricing clarity███████████████37/50
Billing predictability█████████████████42/50
Spend observability██████████████35/50
Billing / invoice quality███████17/50
Disclosure████████████████40/50
RIGHT OF REPLY
Every provider was sent its full assessment — all 25 criteria, our verdict on each, the exact URL we relied on and why — and given 14 days to correct us before anything was published. This is what came back. 1 of 10 replied.
A provider that did not reply has neither endorsed nor disputed these scores, and we do not read anything into the silence. A correction sent after the window still gets acted on: send it to [email protected] and we will re-score and say that we did.
| Provider | Right of reply |
|---|---|
| Anthropic | Contacted 2026-08-28 via email [email protected], then email [email protected] (their support pointed us to the contact channels on their website). No reply within the 14-day window (closed 2026-09-11).Support agent, not a human position: said the enquiry is out of scope for customer support and pointed us to the contact channels on their website. Disputed no criterion. |
| OpenAI | Contacted 2026-08-28 via help.openai.com support chat, then email [email protected] (routed there by their own support). Replied.Case 13935228, reply 2026-08-29 from [email protected]. Reviewed all seven disputed criteria (A3, C5, D1, D2, D4, D5, E2) and submitted no correction: no additional public evidence to change any classification. Explicitly endorsed the NOT VERIFIABLE reading on D4 and E2. Confirmed that from invoices issued 2026-04-01, detailed API costs are no longer on Enterprise invoices. Scope limited to published documentation. |
| Contacted 2026-08-31 via [email protected] from a personal Gmail address on 2026-08-31 (three deliveries from our own domain on 2026-08-28 bounced; Google Cloud billing support case 74848114 opened the same day was closed as out of scope). No reply within the 14-day window (closed 2026-09-14).[email protected] returned only its automatic acknowledgement. Cloud Billing Support had closed case 74848114 as out of scope: no channel to forward external assessments to press or documentation teams, pointing us back to the press address that had bounced. | |
| DeepSeek | Contacted 2026-08-28 via email [email protected]. No reply within the 14-day window (closed 2026-09-11). |
| Mistral AI | Contacted 2026-08-28 via email [email protected]. No reply within the 14-day window (closed 2026-09-11). |
| xAI | Contacted 2026-08-28 via email [email protected]. No reply within the 14-day window (closed 2026-09-11). |
| Cohere | Contacted 2026-08-28 via email [email protected]. No reply within the 14-day window (closed 2026-09-11). |
| AWS Bedrock | Contacted 2026-08-28 via AWS support case 178791375200321 (Billing / Other Billing Questions, opened 2026-08-28). No reply within the 14-day window (closed 2026-09-11).Billing support agent, not a company position, replied 2026-09-15 (after the window had closed): said the enquiry is outside the scope of billing and account support, that it cannot be forwarded or escalated through the support case channel, and pointed us to press.aboutamazon.com/contact-us. Disputed no criterion. |
| Azure OpenAI | Contacted 2026-08-28 via email [email protected]. No reply within the 14-day window (closed 2026-09-11). |
| OpenRouter | Contacted 2026-08-28 via email [email protected]. No reply within the 14-day window (closed 2026-09-11).Support agent, not a company position, replied 2026-09-21 (after the window had closed): said this inbox is the customer support queue and not the right place for media inquiries, and offered no alternative channel. Disputed no criterion. |