Connect providers

The AI Spend Agent pulls usage and billing data directly from your AI provider using an admin API key. You manage connections from inside the agent: connect a provider, rotate its key when it changes, or disconnect it when you no longer want the agent to audit that account.

​

Prerequisites

• The AI Spend Agent must be enabled on your Dash.fi account. See Overview.
• You need an admin key (not a regular API key) from each provider you want to connect. Only an account owner or admin on the provider side can generate one.

​

Open the Configure modal

1. Sign in to app.dash.fi.
2. Open AI Spend Agent from the agents list on your dashboard.
3. Click Configure in the top bar of the agent.

The Configure modal walks you through the connection in four steps: get the admin key from the provider console, paste it into Dash.fi, (optionally) upload your recent provider invoices for billing reconciliation, and (optionally) set daily, weekly, or monthly spend targets. Only the connection is required to activate the agent. The invoice and spend-target steps can be skipped or completed later. Once you’ve connected at least one provider, opening Configure again lands you directly on the manage step for that provider.

​

Connect Anthropic

​

Connect OpenAI

​

Upload invoices (optional)

The third step of the Configure modal lets you upload recent provider invoices so the agent can reconcile them against the usage it pulls from the admin key. This step is optional — the agent activates as soon as a provider is connected, and clicking Next through the invoice step effectively skips it. You can return to Configure at any time to add invoices later. Uploading invoices tightens the accuracy of the reconciliation summary and refund claims in Recovery, because the agent can compare the provider’s actual line-item charges (not just the usage feed) against expected pricing.

​

Supported providers and formats

• Providers: Anthropic and OpenAI.
• File types: PDF or CSV.
• Recommended scope: your last 3 months of invoices for each provider.

​

Upload an invoice

Each row in the Uploaded list shows the filename, tagged provider, upload date, and current status:

• Stored (green check) — The file reached storage and has been recorded against your account.
• Pending — Upload is still being verified.
• Error (red) — The upload didn’t complete. Click Try again to re-select the file.

​

What happens after upload

Uploaded invoices feed the AI Spend Agent’s billing reconciliation pipeline. The next audit compares each invoice’s line items against the expected pricing derived from your usage. Any additional discrepancies surface in the Violations view — specifically under Billing — and back new or refined refund claims in Recovery. You don’t need to do anything else to the uploaded files. There’s no parsing job to poll and no manual mapping step.

​

Set spend targets (optional)

The fourth step of the Configure modal lets you declare what you expect to spend across your connected providers. Targets are measured against aggregated spend across all providers, not per-provider. This step is optional, and setting a target on one window doesn’t require setting one on the others. You can set three independent targets:

• Daily — cost you expect per day.
• Weekly — cost you expect per week.
• Monthly — cost you expect per month.

A window with no target simply gets no spend alerts for that granularity. Set only the windows you care about.

​

Set or update a target

To remove a target, click Clear on its card. That window goes back to No target and stops producing spend alerts.

​

What targets do today

Targets tell the AI Spend Agent what “normal” spend looks like for your team. When aggregate spend in a window runs over its target, the agent surfaces a spend alert under Anomalies. Windows without a target are excluded from that alerting entirely. Editing targets requires the agent:write permission. Team members with read-only access see the current amounts but not the inputs.

​

Sync now

Usage refreshes automatically on the agent’s own schedule. To pull the latest data on demand — for example, after a large spike or before opening a claim — click Sync now next to the connected provider in the Configure modal. The sync runs in the background; usage-based views refetch once it finishes.

​

Connection sync health

Each connection in the Configure modal shows a chip next to the provider name that tells you the state of the last background sync. Use it to tell at a glance whether the numbers in the dashboard are current.

• Connected (green) — The last sync succeeded. Below the key preview, the connection shows Last synced <timestamp> so you know how fresh the data is.
• Sync issue (amber) — The last sync failed on something transient (for example, a provider timeout or upstream 5xx). Dash.fi keeps retrying automatically on the normal schedule. No action is required unless the state persists.
• Action needed (red) — The stored admin key permanently fails, either because the provider rejected it (revoked or expired) or because it can no longer be decrypted. Syncing is paused for that connection and its data is frozen at the last successful sync until you rotate the key.

When any connected provider is in the Action needed state, an amber banner appears on every AI Spend Agent page naming the provider and the date its data froze at, with a Rotate key button that opens the Configure modal on the affected connection. The agent’s top-bar status also switches to amber and appends · action needed to make the state visible without opening Configure. Rotating the key clears the state as soon as the next sync succeeds: the chip returns to Connected, the banner disappears, and the top-bar status goes back to its normal live label. Follow Rotate a key below to paste the new key.

​

Refresh insights

Sync now brings in fresh usage data, but a separate audit pass produces findings and claims. Use Refresh insights (in the agent’s top bar) to re-run the audit against the current usage and produce updated findings. The button shows an Auditing… state while the job runs, and refreshes the Action Plan and Recovery views the moment it finishes.

​

Rotate a key

Rotate a key when the provider-side key is regenerated, revoked, or scheduled to expire. Rotating replaces the stored key without losing any historical data.

​

Disconnect a provider

Disconnecting stops the agent from pulling new usage from that provider. Historical usage and findings already synced remain visible in the dashboard. If you disconnect every provider, the agent falls back to its onboarding screen the next time you open it. Reconnecting later resumes syncs from the moment you connect — there’s no back-fill for the disconnected window unless the provider itself retains that history.

​

Troubleshooting