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 credential when the feature is available. The console attempts a history import; coverage varies by vendor and may contain gaps. Visits and manual refreshes can update the report.
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 | Admin credential accepted by the offered setup flow | Daily spend and available per-key attribution |
| Anthropic | Admin key or supported org:admin OAuth credential | Daily spend and estimated per-key attribution |
| OpenRouter | Management API key, previously called a provisioning key | Available daily activity for the last 30 completed UTC days |
Use the least privilege supported by the vendor and the offered setup flow. A successful connection check does not certify that a credential is read-only. Anthropic Console admin keys have broad administrative access; its supported OAuth credentials also require the stated organization scope. Do not substitute a more powerful credential to troubleshoot an unavailable service.
OpenRouter’s daily activity endpoint requires a Management API key. The current importer does not populate a spending report from a normal inference key, even if that key passes verification. Management keys can manage other keys; they are not ordinary inference credentials. See the vendor’s Management API key guidance .
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.
Attribution depends on the vendor’s cost and usage reports. Anthropic per-key dollar figures are estimates derived from those reports; they are not vendor-reported per-key invoices. Unreliable attribution is withheld, and unattributed costs remain separate. Discounts or later corrections can affect the imported figures.
Historical totals and per-key breakdowns are limited by successful vendor imports. There is no universal December 2025 start date for OpenAI per-key usage. Check the reported gaps and sync status before treating an older range as complete.
Freshness
- Connecting a vendor starts a background import. The default requested range is up to 12 months, with a shorter OpenRouter range; this is not a guarantee of coverage.
- A visit starts a refresh when data is older than 6 hours. This does not establish a recurring refresh while nobody visits the page. Manual refresh is also offered.
- The most recent 3 days are re-fetched on every sync, so late vendor restatements are picked up.
Credential handling
- The retained implementation seals credentials with AES-256-GCM before storage and decrypts them for synchronization.
- Customer-facing pages and connection API responses do not return stored credentials; they show metadata such as the last four characters instead. This is not a promise about every form of operator access.
- Disconnecting clears the active connection’s stored credential. Imported history is retained unless its deletion is requested through the offered purge control. Disconnect alone does not prove backup erasure or cancellation of an in-flight sync.
The full policy is published on the Platform at /spend/credentials-policy.
Organizations
Choose the intended personal or organization context before connecting a vendor. Connections and reports are stored against that context. Organization connection controls require an owner or admin; the spend API checks membership for reads and refreshes. Current service access, including access after membership changes, still needs Platform-owner verification. A shared date-range link does not grant access to another account’s report.