Cloudflare AI Gateway
Daily totals per model, upstream provider and gateway: requests, input and output tokens, cache reads, errors and the cost Cloudflare computed. Never a request body, never a response.
Access
- Kind
- A read-only key you paste
- What to give
- Read-only API token and account ID
- Why that one
- An API token with AI Gateway Read on the account. Valistry calls only the GraphQL analytics endpoint, a read.
What it attributes on its own
- From the source
- day · model · upstream provider · gateway · requests · input and output tokens · cache reads · errors · what Cloudflare computed the day cost
- Needs a rule or a trace
- the provider's invoice — Cloudflare computes a cost, it does not bill you for inference · team, workflow and agent unless a rule maps the gateway · outcome
The addresses it calls
- https://api.cloudflare.com/client/v4/graphql
Only these. A call anywhere else is refused before it leaves, and every call is logged.
Connecting it
- Copy your account ID. It is on the right of any account page, a 32-character value. Open ↗
- Create an API token with one permission. Use Create Custom Token and fill the form: Open ↗
- Paste both and click Test and connect. Valistry reads the last seven days of gateway analytics, reports what it found, then fills thirty.
Cloudflare computes a cost; the provider bills it. Connecting both this gateway and a provider behind it counts the same request twice — connect one.