When you connect Cursor, OpenAI, or Claude Platform to Torii, the AI Module also syncs cost for that platform directly from the vendor's official admin API. This gives you billed cost figures that refresh on their own every day, without anyone needing to run a manual sync.
There is nothing extra to install and no new integration to connect. Torii uses the credentials from the integration you already connected.
Supported platforms
Cost sync covers Cursor, OpenAI, and Claude Platform (connected in Torii as the Claude Developer integration).
For the other AI platforms, cost and usage come from the Torii AI Lens browser extension. For developer command-line tools such as Claude Code, Gemini CLI, and Codex, use AI Telemetry.
What you need
- The AI Module enabled for your organization.
- The relevant integration connected in Torii with an admin-level credential:
- Cursor - Admin API Key
- OpenAI - Admin Key and Organization ID
- Claude Platform - Admin API Key (must start with
sk-ant-admin...)
See Cursor Integration, OpenAI Integration, and Claude Developer Integration for how to generate these values and connect each integration.
What Torii syncs
| Platform | Cost data synced | Cost per user |
|---|---|---|
| Cursor | Daily on-demand (usage-based) cost | Not available |
| OpenAI | Daily cost, broken down by project and by model or service | Not available |
| Claude Platform | Daily cost, broken down by model and workspace | Available |
- Cost data is refreshed once a day.
- Torii reports both the last 30 days and the last 12 months.
- Cost is retrieved from each vendor's API in USD, and reflects the amounts the vendor bills you rather than an estimated token value.
- If you have connected more than one account for a platform, Torii combines them into a single organization total.
How this works alongside AI Lens
The admin API sync is an additional cost source, not a replacement for the Torii AI Lens browser extension. AI Lens continues to sync members, API keys, model usage, billing, and workspaces for these platforms, and remains the cost source when the integration is not connected in Torii.
For Cursor the two work together. The Cursor page separates Subscription - your recurring seat charge, taken from your billed invoices - from On-demand usage charges synced from the Cursor Admin API, and shows the combined total.
When data appears
The sync runs once a day, so the first cost data appears within 24 hours of connecting the integration.
For Cursor, the 12-month history builds up over roughly the first two weeks, because Cursor's API limits how much history can be retrieved per run. The last-30-days figure is available right away.
Frequently asked questions
Do I need to connect a new integration to get AI cost data?
No. Torii uses the admin credential from your existing Cursor, OpenAI, or Claude Developer integration. If the integration is already connected and the AI Module is enabled, no action is needed.
Is Claude Platform the same as Claude.ai?
No. Claude Platform is the Anthropic Console and API product, billed per token, and is connected in Torii as the Claude Developer integration. Claude.ai is the seat-based chat product. They are billed separately by Anthropic, connect separately in Torii, and have their own pages in the AI Module.
Why is there no cost per user for Cursor and OpenAI?
Those vendors' cost APIs report cost at the organization, project, and model level, with no user dimension. Claude Platform reports token usage per identity, so Torii can attribute cost per user there.
Is usage data such as sessions, prompts, or accepted lines included?
No. This sync provides cost data. Usage and productivity metrics come from the Torii AI Lens browser extension and AI Telemetry.