Stored in Tollgate
- Project, environment, and customer ID
- Idempotency key and safe trace IDs
- Provider and requested/reported model
- Token counts and available raw cost
- Latency, status and safe tool names
- Applied pricing and fixed billing-run totals
Customer metering contract / V1
Know what crosses
the gate.
Four provider adaptersTest and live environmentsCustomer-aware pricingPrivate metadata mode
01 / Request path
One request. One customer.
- Your client
Sends a supported non-streaming request with a provider key,
X-Tollgate-Key,X-Tollgate-Idempotency-Key, andX-Tollgate-Customer. - Tollgate
Checks the project write key and retry ID before provider spend, uses the selected adapter, records safe usage metadata once, then returns the provider response.
- Your provider
Runs the model and remains the authority for provider charges. Tollgate does not resell inference.
02 / Data boundary
Metadata stays.
Content does not.
Never persisted
- Provider API key
- Authorization header
- Prompt or message content
- Model response content
- Tool arguments or payloads
Your key, prompt and response pass through Tollgate memory for the request. “Never persisted” does not mean Tollgate never processes them.
03 / Billing loop
Raw usage becomes a fixed monthly charge.
Match each supported call to a customer record or make unattributed usage visible.
Keep test and live usage separate, reject duplicate retry IDs, and show invalid or unpriced events.
Apply a customer override or default rule, with optional base charges, included tokens, and exact model rate cards.
Freeze a completed month, download its CSV, or create Stripe draft invoices for mapped customers.
04 / Current limits
What Tollgate does not claim.
- Connected endpoints are non-streaming OpenAI and OpenRouter Chat Completions, Anthropic Messages, and Gemini GenerateContent.
- A safe model ID can pass through only within those four request formats. Streaming and other endpoints, including OpenAI Responses, are not supported.
- Provider origins and paths are fixed. Other hosted providers are not connected.
- Reported provider cost, verified OpenAI estimates, or an exact rate card can price usage. Otherwise cost stays unavailable; provider invoices remain authoritative.
- Any proxy adds some overhead. Tollgate records end-to-end latency but does not yet publish isolated proxy overhead.
- Billing runs are fixed Tollgate records, not legal tax invoices. CSV export and Stripe draft creation are supported.
- Tollgate does not send invoices, collect payment, calculate tax, manage subscriptions, prorate charges, issue credits, or recover failed payments.
- Recovery-code access is intended for the private beta; team accounts, roles, and single sign-on are not available.
One customer ID. One fixed billing run. One Stripe draft.