AI Spend Console
Under maintenance. The managed Vinci API and Platform are under maintenance. These service-specific instructions are retained as reference for existing integrations when service is available. They do not promise current access or a return date. Downloadable models and direct/BYOK use of Vinci Code CLI are separate paths.
The AI Spend Console shows what you spend across AI vendors — Anthropic, OpenAI, OpenRouter, and Vinci — on one dashboard, day by day. Connect a vendor with an API key and the console backfills up to 12 months of history, then keeps itself fresh automatically.
It appears as AI Spend in the Platform sidebar, at /spend.
Connect a vendor
Open AI Spend → Connect and paste a key for each vendor you want to track. Every key is verified with the vendor before it is stored — an invalid key is never saved. Your Vinci spend is built in and needs no connection.
| Vendor | Key to use | What you get |
|---|---|---|
| OpenAI | Read-only admin key | Daily spend with per-key breakdown |
| Anthropic | Admin key | Daily spend with per-key breakdown |
| OpenRouter | Normal key or provisioning key | Totals only with a normal key; daily breakdown with a provisioning key |
Note: Anthropic does not offer a read-only admin key, so connecting Anthropic uses a full admin key — one that can also manage members and workspaces. The connect flow states this before you paste anything. OpenRouter retains roughly 30 days of daily history, so older OpenRouter days cannot be backfilled.
Reading the dashboard
- One chart for every vendor. Daily spend is stacked by default; toggle to a grouped view to compare vendors side by side. As the range grows, the chart switches from daily to weekly to monthly marks automatically.
- Date ranges live in the URL. Choose a 7-, 30-, 90-day, or 12-month preset, or a custom start and end date. A pasted link shows the recipient the same period.
- Summary tiles show spend this period, a projected period-end figure based on your run rate, your largest vendor, and how much of the total is attributed — each with a change against the previous period.
- Per-vendor cards show the vendor’s total, share of the period, connection status, the last four characters of the connected key, when data was last synced, and any days that could not be fetched.
Honest numbers
The console labels what it knows and says what it does not:
- Days that could not be fetched are named as gaps, never drawn as $0.
- A total that is knowably short is labelled as a floor, not presented as complete.
- A breakdown the console cannot stand behind is withheld rather than guessed.
- Dollars that cannot be attributed to a key are shown as their own unattributed row — never spread across the keys it can see.
Per-key dollar figures are derived from your own vendor cost reports, so negotiated discounts and price changes are reflected automatically. For Anthropic this produces per-API-key dollar amounts that Anthropic’s own console does not report.
Note: OpenAI’s API does not report per-key usage before December 2025, so the per-key breakdown for OpenAI starts there even though totals go back further.
Freshness
- Connecting a vendor starts a background backfill of up to 12 months.
- On each visit, data older than 6 hours is refreshed automatically.
- The most recent 3 days are re-fetched on every sync, so late vendor restatements are picked up.
Credential handling
- Credentials are sealed with AES-256-GCM before storage and are decrypted only transiently while verifying or syncing.
- No page, API response, or support channel can read a stored key back. Only the last four characters are ever shown again.
- Disconnecting a vendor wipes the stored ciphertext in the same operation.
The full policy is published on the Platform at /spend/credentials-policy.
Organizations
In an organization context, spend connections and charts belong to the organization and are visible to its members. Only an owner or admin can connect or disconnect a vendor; any member can view and refresh. Personal and organization spend are kept fully separate.