Connect OpenAI, Anthropic, Datadog and Snowflake

Connect AI and software vendors with admin keys or a Snowflake key pair so their spend sits beside your cloud costs.

Connect OpenAI, Anthropic, Datadog and Snowflake

Bring AI and software-vendor spend into the same view as your cloud bills, by pasting a read-only key (or, for Snowflake, registering a key pair) for each vendor.

Where in CostGlassCost Explorer → SaaS & AI Spend → Connect Provider
PlanDepends on your plan's connection limit
Who can do thisAny signed-in member of your CostGlass organisation, plus someone who can create admin keys in the vendor
Time needed3 to 10 minutes per vendor
In short
  • All four connect from one dialog: SaaS & AI Spend → Connect Provider. Pick the vendor, give the connector a name and supply its credentials.
  • Every credential is checked against the vendor before it is stored. A wrong key is rejected on the spot with the vendor's own message, not discovered six hours later.
  • OpenAI and Anthropic need an Admin key (a normal project or workspace key is not enough). Datadog needs an API key and an application key. Snowflake uses a key pair that CostGlass generates, plus an organisation administrator.
  • Spend is read every six hours. OpenAI, Anthropic and Snowflake are daily; Datadog is monthly.
  • Personal ChatGPT and Claude subscriptions cannot be connected, because they have no cost report.

Where it fits

Cloud bills are only part of modern spend. Language-model usage and monitoring or data-warehouse tools often arrive as separate invoices with little breakdown. Connecting them puts their spend into the same cost data as your clouds, so it shows up in Cost Explorer, Reports and the dashboard. The page itself is described in SaaS and AI spend.

VendorWhat you provideData granularitySource
OpenAIAn Admin API key (starts sk-admin-)Daily, per project and line itemOpenAI's organisation Costs API
AnthropicAn Admin key (starts sk-ant-admin01-)Daily, per workspace, model and token typeAnthropic's organisation Cost Report API
DatadogAPI key + Application key + siteMonthly (current and previous month), per productDatadog's Estimated Cost API
SnowflakeA key pair you register, plus account identifier and usernameDaily, in real currencySNOWFLAKE.ORGANIZATION_USAGE.USAGE_IN_CURRENCY_DAILY
Note
The connect dialog also lists DeepSeek (Direct API) with a normal API key. It follows the same paste-and-verify pattern, but this guide covers the four vendors above.

The connect dialog

Go to SaaS & AI Spend and click Connect Provider. The dialog is called Connect SaaS / LLM Provider.

FieldWhat to enter
ProviderOpenAI (Admin API), Anthropic Claude (Admin API), DeepSeek (Direct API), Datadog (Estimated Cost API) or Snowflake (ORGANIZATION_USAGE).
Connector NameAny name you like, for example "Production OpenAI". Names are unique per vendor within your organisation: reusing one replaces that connector's credentials.
API key fieldIts label changes with the vendor: OpenAI Admin API Key, Anthropic Admin Key or Datadog API Key.
Datadog Application KeyDatadog only.
Datadog SiteDatadog only. Choose the site you sign in to.

Click Connect & Sync. It shows Verifying & Connecting… while CostGlass makes one small real call to the vendor. Only if that succeeds is the credential saved (in CostGlass's encrypted secrets store), a connector card created and a first sync run. Snowflake has its own two-step flow, described below.

Only one connector per vendor is synced
You can create connectors with different names, but each scheduled sync reads the first active connector for a vendor. Connect one connector per vendor.

OpenAI

You need
  • An OpenAI organisation owner (only owners can create Admin keys).
  • An OpenAI Admin API key, which starts with sk-admin-. A regular project key is rejected with a message telling you which kind of key is needed.
1
Create an Admin key
In the OpenAI platform go to Settings → Organization → Admin keys and create a key named something like costglass-readonly. Copy it straight away.
2
Connect it
Open Connect Provider, choose OpenAI (Admin API), enter a Connector Name, paste the key into OpenAI Admin API Key (sk-admin-...) and click Connect & Sync.
SaaS & AI Spend → Connect Provider → OpenAI.

CostGlass reads OpenAI's organisation cost report in daily buckets, grouped by line item and project. Amounts are real dollars as OpenAI reports them. Each sync reads roughly the last 35 days. Token volumes and the share of requests sent through the Batch API appear beside the dollars.

Anthropic

You need
  • An Anthropic organisation admin.
  • An Admin key, which starts with sk-ant-admin01-. Admin keys exist only for organisation accounts. An individual (personal) account cannot create one, so it cannot be connected.
1
Create an Admin key
In the Claude Console go to Settings → Admin Keys and create a key.
2
Connect it
Open Connect Provider, choose Anthropic Claude (Admin API), enter a name, paste the key into Anthropic Admin Key (sk-ant-admin01-...) and click Connect & Sync.
SaaS & AI Spend → Connect Provider → Anthropic.

CostGlass reads Anthropic's cost report in daily buckets, grouped by description and workspace. Cost is shown per workspace, model and token type (uncached input, cache reads, cache writes and output), so you can see how well prompt caching is working. A brand-new organisation with no usage shows nothing yet.

Datadog

You need
  • A Datadog administrator who can create API and application keys.
  • A Datadog API key.
  • A Datadog application key with the usage_read scope.
  • Your Datadog site, for example datadoghq.com or datadoghq.eu.
1
Create the two keys
In Datadog, open Organization Settings → API Keys for the API key and Application Keys → New Key for the application key. Name the application key costglass-finops-readonly and grant it only the usage_read scope. Do not use a key that belongs to a person: when they leave, your billing data would quietly stop.
2
Find your site
It is in the URL when you are signed in, for example datadoghq.com, datadoghq.eu or us3.datadoghq.com. Keys do not work across sites.
3
Connect it
Open Connect Provider, choose Datadog (Estimated Cost API), enter a name, paste Datadog API Key and Datadog Application Key, choose the Datadog Site and click Connect & Sync. CostGlass checks both keys against Datadog first.
SaaS & AI Spend → Connect Provider → Datadog: API key, application key and site.

The site choices are:

datadoghq.com, datadoghq.eu, us3.datadoghq.com, us5.datadoghq.com, ap1.datadoghq.com, ap2.datadoghq.com and ddog-gov.com.

What Datadog gives CostGlass

  • Estimated cost per product (hosts, logs, custom metrics and so on) for the current and previous calendar month only. Datadog does not provide older history through this API.
  • One figure per product per month, so there are no daily Datadog numbers and no daily anomaly detection for it.
  • Datadog's own figures can lag by up to 72 hours and are estimates until the month closes.
A 403 error
A 403 almost always means the application key is missing the usage_read scope, or the wrong site is selected. CostGlass shows the message when you connect.

Snowflake

Snowflake does not use a pasted password. CostGlass generates an RSA key pair for the connection, keeps the private key in its encrypted vault and gives you the public key to register on a Snowflake user. CostGlass then signs in with that key.

You need
  • Someone who can alter a Snowflake user (a user administrator) to register the public key.
  • Your account identifier, for example xy12345.eu-west-1, and the username CostGlass will connect as.
  • Access to SNOWFLAKE.ORGANIZATION_USAGE for that user. An organisation administrator (ORGADMIN) has to grant it. This is the step most people miss.
1
Generate the key pair
Open Connect Provider, choose Snowflake, enter a Connector Name and click Generate Keypair.
SaaS & AI Spend → Connect Provider → Snowflake, step one.
2
Register the public key in Snowflake
CostGlass shows one SQL statement. Replace the username placeholder with the Snowflake user CostGlass should connect as and run it in a Snowflake worksheet as a user administrator.
Run in Snowflake
3
Enter the account and verify
Back in CostGlass fill in Account Identifier and Snowflake Username, then click Verify & Sync. It reads Verifying Connection… while CostGlass signs in with the key and runs a small query.

The ORGADMIN requirement

CostGlass reads real currency amounts from SNOWFLAKE.ORGANIZATION_USAGE.USAGE_IN_CURRENCY_DAILY, because credits alone cannot be priced reliably. Ordinary roles cannot see this view. An ORGADMIN must grant the connecting user's role access to it. If access is missing, verification or the sync stops with a message that names this requirement. CostGlass never swaps in a different view or a made-up number instead.

The connect form uses the user's default role. If you need a specific role or warehouse, make it that user's default in Snowflake before you verify.

Snowflake data is daily and each sync reads roughly the last 35 days. Registering the public key and the ORGADMIN grant are the only changes made in your Snowflake account, and both are yours to make.

After you connect

  • Each connected vendor appears as a card with its status (active, pending or error), the 30-day recorded spend, the time of the last sync and any error message.
  • CostGlass syncs every six hours. Click Sync on a card to sync that vendor now.
  • The trash icon removes the connector after you confirm. Its stored credentials are deleted; cost already collected is kept.
  • Spend is stored alongside your cloud costs, so you can filter by these vendors in Cost Explorer and Reports. Budgets, anomaly detection (for daily vendors) and savings checks (for example moving eligible OpenAI work to Batch, or prompt caching for Anthropic) cover them too.
  • Seat activity and token detail appear where the vendor exposes them. Where it does not, the page says so rather than showing a guess.

Limits worth knowing

LimitDetail
Personal subscriptionsA Claude.ai or ChatGPT plan (Pro, Max, Plus and similar) is not API usage and has no cost report. CostGlass reads the organisation-level Admin cost reports, and Anthropic issues Admin keys only to organisation accounts. Connect the API organisation you build with instead.
Admin keys onlyOpenAI and Anthropic normal keys cannot read organisation cost. They are rejected at connect time.
Datadog historyCurrent and previous month only, monthly granularity, up to 72 hours late.
Snowflake permissionNeeds an ORGADMIN grant on ORGANIZATION_USAGE.
CurrencyThese vendors bill in dollars as reported. Figures are shown in your chosen display currency using the usual rates.
Live-vendor testingThese connectors were built against each vendor's documentation. If your first sync fails with something unexpected, tell CostGlass support.

Questions people ask

Why was my OpenAI key rejected?
You probably pasted a project key. Create an Admin key (Settings → Organization → Admin keys) that starts with sk-admin-.
Can I connect my personal Claude or ChatGPT subscription?
No. Those plans have no cost report. Only API organisations with Admin keys can be connected.
Datadog says 403.
Check the application key has the usage_read scope and that the Datadog Site matches the URL you sign in to.
Snowflake verification fails with a permission message.
Ask an ORGADMIN to grant the connecting role access to the SNOWFLAKE.ORGANIZATION_USAGE views.
Why is Datadog only two months?
The estimated-cost API only returns the current and previous month. CostGlass builds history from each sync going forward.
Is my key stored safely?
Keys are stored only in CostGlass's encrypted secrets store, are never returned by any screen, and are verified before storage.

Related guides