> ## Documentation Index
> Fetch the complete documentation index at: https://docs.guild.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect spend platforms

> Sync billed spend from Anthropic, OpenAI, and Cursor into the Insights Platform dashboard.

[Platform spend](/insights/platform-spend) charts what your team spends on external LLM platforms alongside the usage Guild records from its own runtime. Guild's own usage needs no key. To bring in what a platform bills you directly — console traffic, direct API calls, a coding tool your developers pay for — connect that platform with an admin key.

Guild reads usage and cost reports from three platforms today:

* **Anthropic**
* **OpenAI**
* **Cursor**

Access follows the Insights dashboard: a personal account's owner, or an organization's admins.

## Connecting a platform

<Steps>
  <Step title="Open the dialog">On **Insights → Platform**, choose **Manage platforms**.</Step>
  <Step title="Create an admin key">Create a key on the platform, following the guidance in the table below.</Step>
  <Step title="Paste it into Guild">Select the platform, paste the key, and save.</Step>
</Steps>

Guild validates a key when you save it, stores it server-side, and never shows it again. Spend syncs hourly, and a fresh sync's data appears within a few minutes. **Sync** forces one.

## Which key each platform needs

| Platform      | Key                            | Where to create it                                          | Can you scope it down?                                                                     |
| ------------- | ------------------------------ | ----------------------------------------------------------- | ------------------------------------------------------------------------------------------ |
| **Anthropic** | Admin key (`sk-ant-admin01-…`) | Anthropic Console → Settings → Admin keys. Org admins only. | No — console admin keys carry full admin access.                                           |
| **OpenAI**    | Admin key (`sk-admin-…`)       | OpenAI platform → Settings → Organization → Admin keys.     | Yes — set the key to **Read only**, or **Restricted** with just the usage and cost scopes. |
| **Cursor**    | Admin API key (`key_…`)        | Cursor dashboard → API Keys. Team admins only.              | No — Cursor admin keys carry full admin access.                                            |

Guild only ever reads usage and cost reports with these keys.

<Warning>
  Anthropic and Cursor admin keys cannot be narrowed, so each one grants full admin access to that account. Store them accordingly and rotate any key you think has been exposed. Where a platform does allow narrowing, as OpenAI does, grant the least it will accept.
</Warning>

Removing a key stops new imports. Spend already synced stays on the dashboard.

## How spend is attributed

A model bought through one platform is often served by another, so the dashboard offers two ways to group the same spend. Switch between them with the **Platform** and **Provider** tabs in the breakdown card.

* **Platform** groups spend by who billed it. Claude usage bought through Cursor counts as Cursor, because Cursor is what invoices you. Use this tab to reconcile against your invoices.
* **Provider** groups spend by the model's actual provider. That same Claude usage counts as Anthropic. Cursor's own models — ids beginning `cursor` or `composer`, plus its `auto` and `default` routing ids — stay under Cursor, and a model Guild does not recognize falls under **Other**. Use this tab to compare what you spend across model providers.

Guild-routed traffic is subtracted from each platform's bill, so usage Guild already records is not counted twice.