Connect an existing provider
Connect OpenAI, Anthropic, and other provider accounts so SuperPenguin can pull billed usage.
Customer teams connect provider admin credentials in the SuperPenguin dashboard so billed usage and cost can be synced for reconciliation and coverage checks.
Typical flow
- Open Integrations / Connections in the dashboard.
- Choose the provider (OpenAI, Anthropic, Deepgram, ElevenLabs, Cursor, cloud billing connectors, and others as listed in-product).
- Follow the provider-specific credential steps (API key, OAuth, or cloud role).
- Wait for the initial backfill, then confirm recent billed rows appear.
Credentials are stored encrypted. SuperPenguin uses them only for read-oriented billing and usage syncs defined by that integration.
SDK vs connection
| Path | Purpose |
|---|---|
| SDK wrap | Per-request attribution and estimated cost |
| Hosted OTLP / OpenRouter Broadcast | Per-request attribution from provider/exporter traces |
| Provider connection | Provider-billed usage/cost for reconciliation |
You usually want one request-attribution path (SDK or hosted OTLP) plus a provider connection for invoice truth. Broadcast sampling, credits, settlement, and BYOK mean request rows are not a guaranteed invoice feed.
Building a provider API instead?
If you are a provider implementing export endpoints for SuperPenguin (and other FinOps clients), go to Build a billing integration. That path is unrelated to pasting an admin API key into the dashboard.