Vendor billing verification
Know when a provider bills you wrong
See it working
- example-delta3 mismatches
- Checked
- 28
- Billed right
- 25
- Can't verify
- 0
- Managed
- 9
3 charged for a miss · 3 credits ($0.012) overbilled
- example-gamma1 mismatch
- Checked
- 52
- Billed right
- 51
- Can't verify
- 0
- Managed
- 18
1 double-charged · 1 credit ($0.007) overbilled
- example-alphaAll billed right
- Checked
- 119
- Billed right
- 119
- Can't verify
- 0
- Managed
- 46
- example-zetaAll billed right
- Checked
- 65
- Billed right
- 65
- Can't verify
- 0
- Managed
- 24
- example-betaAll billed right
- Checked
- 50
- Billed right
- 50
- Can't verify
- 0
- Managed
- 7
What you get
Expected vs charged, per call
The credits and dollars the provider's rule expects next to what it reported, on every call made with your key.
Clear verdicts
ok, charged for a miss, double-charged retry, price mismatch, or can't verify when the provider reports nothing.
The rule, cited
Each call's detail shows the provider's billing rule in plain English, with a link to its pricing page.
Billing accuracy by provider
Calls checked, billed right and overbilled, in credits and dollars, for any filter and window.
Dispute export
The mismatches as a CSV with request id, UTC time, endpoint, expected and reported credits: ready to send to the provider.
How it works
Call providers with your own vendor keys, as usual.
GridRouter reads the charge each provider reports and checks it against its published rule.
Filter billing:mismatch, review the calls, and export the disputes.
curl "https://api.gridrouter.io/v1/logs/billing?from=2026-09-01T00:00:00Z" \
-H "Authorization: Bearer $GRID_API_KEY"
# { "by_provider": [ { "provider": "…", "checked": 1204, "ok": 1181,
# "charged_for_miss": 23, "impact_micro": 92000 } ] }Questions
Which providers can be checked?
Providers that report usage per call, once their billing rules are researched and cited. Others read can't verify, and the call detail says why.
What about managed calls?
Managed calls run on GridRouter's own vendor accounts, so what the provider charged is our cost, not your bill. They read managed and aren't broken down.
Does GridRouter dispute charges for me?
No. You get the evidence: the export lists each mismatched call with the provider's own request id and the rule it broke.
More in GridRouter
- Unified API and routingAsk for a capability, not a provider. GridRouter picks the provider, falls back on a miss or an error, and answers in one schema.
- MCP serverPoint any MCP client at one URL and your agent can search the catalog, get a quote and call any capability, inside the budget you set.
- WaterfallsPut providers in order, choose how fast and how far to go, and publish the result as a versioned endpoint your code and agents can call.
- Logs and log explorerSee exactly what every provider returned, what it cost and how long it took, from the dashboard, the API, the CLI or your agent.
- Private cacheStop paying twice for the same person or company. Every answer is cached for your workspace only and reused until its fields expire.
- Alerts, webhooks and integrationsHear about a failing provider, a runaway agent or a wrong charge in seconds, in the tools your team already watches.
- Security and governanceYour vendor keys, data and spend stay inside your workspace, and every change is on the record.
- Provider catalog and docsFind the right provider for a capability, see how it bills and what its API looks like, before you sign a contract.