Providers

Fluxtab syncs usage from OpenAI, Anthropic, and OpenRouter. Each connection stores a label, last sync time, and related metadata. Keys are stored server-side in Supabase Vault and are never returned to the browser.

Why use it

Provider consoles are separate. Connecting them here gives one MTD view, shared alerts, and (where the provider allows) project or workspace attribution — without putting Fluxtab in the request path.

Setup

1. Open Settings → Connections (account owners only on a team plan).
2. Choose a provider and paste the key:
   • OpenAI / Anthropic — an admin or organization key with permission to read usage and costs.
   • OpenRouter — see below; a normal inference API key will not work.
3. Save. Free plans allow one provider connection; Pro/Team can connect all three.
4. Run Sync now on the dashboard (or wait for the schedule).

OpenRouter

OpenRouter requires a separate Management key from OpenRouter → Settings → Management Keys. A standard OpenRouter API key cannot read usage history.

Management keys cannot run inference or spend money the way a normal API key can. History is capped at the last 30 UTC days, regardless of plan — a limitation of OpenRouter’s /activity API. OpenRouter usage has no project/workspace attribution.

Provider notes

| Provider | History | Attribution | | --- | --- | --- | | OpenAI | Follows your plan’s range (7 / 30 / 90 / custom days) | Project grouping when the key can call costs/usage with group_by=project_id | | Anthropic | Same plan range | Workspace mapped to Fluxtab’s project fields when available | | OpenRouter | Last 30 UTC days only | None |

After the first successful sync, Fluxtab may nudge you to check the provider’s own budget settings. Fluxtab alerts on thresholds but cannot stop spend directly, and it cannot verify whether you already configured a native limit. Treat Fluxtab and provider budget UIs as early warning, not a guarantee.