AI & Data

Connect AI Spend (OpenAI + Anthropic)

Pulls AI tooling spend from provider billing/usage admin APIs (OpenAI Costs, Anthropic Cost Report) for spend visibility — the spend input to AI ROI.

What you'll need

An OpenAI admin key and/or an Anthropic admin key (org-level cost/usage, NOT a regular API key) — either is optional on its own, provide the ones you use. This feeds the AI-ROI SPEND input only; grading the AI ROI score also needs adoption (AI-assisted code %) + productivity (hours saved / loaded cost) inputs, so spend alone won't produce a grade.

Credential

Provider admin API key(s) (read-only cost/usage)

Requested scopes

openai:cost:read, anthropic:cost:read

Powers

AI ROI (spend)

What it pulls

Trailing 30-day cost per provider (OpenAI, Anthropic), normalized to a monthly figure, into ai.spend.monthly_usd (per provider) + ai.spend.total_monthly_usd metrics.

What you’ll enter

The exact fields the connect form asks for — and where to find each value.

OpenAI admin API keyoptional
platform.openai.com → Settings → Organization → Admin keys → Create admin key (an admin key, not a regular API key). Optional.
Anthropic admin API keyoptional
console.anthropic.com → Settings → Admin keys → create a key with Cost API read access. Optional — provide either or both.

Step-by-step setup

  1. 1

    Create an OpenAI admin key

    platform.openai.com → Settings → Organization → Admin keys → Create admin key (needs read on the org Costs/Usage API — an admin key, not a regular API key). Copy the sk-admin-… value into OpenAI admin API key.

  2. 2

    Create an Anthropic admin key

    console.anthropic.com → Settings → Admin keys → create a key with Cost API (usage/cost) read access. Copy the sk-ant-admin… value into Anthropic admin API key.

  3. 3

    Provide at least one provider

    Fill OpenAI, Anthropic, or both — each is optional on its own, but you need at least one. Regular (non-admin) keys are rejected. Keys are read-only and encrypted at rest.

  4. 4

    Know what this grades

    This pulls trailing-30-day spend into the AI ROI spend input. The AI ROI grade also needs adoption (from GitHub) + productivity inputs, so spend alone won't generate a score.

  5. 5

    Connect

    Click Connect — we validate each key live against its provider's cost API, encrypt them at rest, and pull trailing-30-day spend.

Create provider admin keys → Connect in the app

Read-only admin key(s), validated live against each provider's cost API, encrypted at rest, then synced into ai.spend.* metrics. Mocked-fetch tested; connect a real key to verify ingestion. Grading the AI ROI score additionally needs adoption (AI-assisted code %) + productivity (hours saved / loaded cost) inputs, so this connector surfaces spend without fabricating a grade.