Set a new password
Your recovery link has verified your identity. Choose a new password, then sign in normally.
See your AI spend.
Understand the activity.
Start with a reported charge and its source. Explore the sample now, then connect your first provider when you have reporting access.
No TokenObserve server to install. Your existing clients use a hosted endpoint.
Provider-reported costs, subscription invoices and gateway estimates keep their own source and currency.
Explore reports here or connect your own tools. Billing alone does not reveal historical conversations.
Sign in to your workspace
Use your verified account to continue.
30 days from workspace creation. No card and no automatic paid conversion. Provider usage is charged separately. Trial details.
Start with one billing source.
Create your workspace, then connect the provider you want to check first. Explore the sample while you arrange reporting access.
- 1Create workspace
- 2Connect billing
- 3Choose how to use it
Reported spend
Reported costs keep their source and currency. Gateway estimates and subscription invoices remain separate.
Full period export uses the date and provider filters. Dimension search applies only to loaded rows.
| Period (UTC) | Source | Project / service | Reported cost |
|---|
Missing coverage is not zero usage. Billing feeds expose costs, not historical prompts or replies. Hidden chain of thought is unavailable.
Connect billing
Start with a provider's organization billing source. Inference uses a separate key.
Add activity and AI search later
Connect activity and AI search
Add an inference key, then point existing clients at your hosted gateway. Saving a key sends no model request.
Need to rotate a saved inference key? Save a replacement for the same provider. Billing credentials cannot be reused here.
Set up API, MCP or gateway access later
Web, API and MCP
Use the same workspace and source-aware reports from your browser or your own tools.
Web dashboard
Inspect conversation evidence, search filters, governance and gateway estimates. Billing connections alone do not supply activity.
Open activity dashboardFor gateway or MCP access, open Agents in your workspace, register an agent and copy its one-time key. You can also create an agent and key through the workspace API using your managed user token. Machine keys cannot manage cloud accounts. Use an active workspace key, never your provider billing credential.
Gateway URLs and native client paths
OpenAI / xAI compatible base URL
Workspace root for native Anthropic and Google clients that add their API paths
Native Anthropic requests use /v1/messages. Native Google requests use /v1beta/models/MODEL:generateContent. Append these paths to the workspace root for direct HTTP requests.
Read reports with the API
The cloud API uses your Supabase user access token. Browser session cookies are not a substitute for a headless Bearer token. Keep tokens out of source control. Discover managed Auth endpoints or read the OpenAPI contract.
Read reports through MCP
Connect an active ACP agent or seat key to the workspace MCP endpoint. Provider-account billing requires explicit report:provider-billing and grants at every delegated hop. Team grants alone do not grant account-wide billing access.
After your MCP client initializes and discovers tools, read the selected report with this call. It does not collect billing or invoke a model.
Each workspace has its own server process, database and application credentials on a shared managed host. The monthly traffic quota pauses portal and gateway access; retained data remains available after the quota is raised or the UTC month renews. Provider feeds can be delayed or incomplete. Private-network tools and endpoint controls require their own supported integration.