Admin keys are stored encrypted and are only used to read usage, cost, and billing data from the provider. Dash.fi never uses them to make model calls on your behalf.
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
- Sign in to app.dash.fi.
- Open AI Spend Agent from the agents list on your dashboard.
- Click Configure in the top bar of the agent.
Connect Anthropic
1
Create an admin key in Anthropic
Sign in to the Anthropic Console and go to Settings > Admin Keys. Create a new admin key and copy it — it’s shown only once.
2
Paste the key into Dash.fi
In the Configure modal, choose Anthropic, paste the admin key, and click Connect.
3
Wait for the first sync
The agent immediately fetches your recent usage. Overview, Usage, and the findings views populate as data lands — the first pass typically completes within a few minutes.
Connect OpenAI
1
Create an admin key in OpenAI
Sign in to the OpenAI Platform and go to Settings > Admin Keys (organization-level). Create a new admin key and copy it — it’s shown only once.
2
Paste the key into Dash.fi
In the Configure modal, choose OpenAI, paste the admin key, and click Connect.
3
Wait for the first sync
The agent begins syncing usage as soon as the key is accepted.
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
1
Open the Upload invoices step
In the Configure modal, advance to Upload invoices (step 3).
2
Choose a provider
Select Anthropic or OpenAI to tag the invoice. You can switch providers between uploads.
3
Pick a file
Click the upload area and choose a PDF or CSV from your machine. The upload starts as soon as you pick the file.
4
Wait for it to finish
A progress bar shows the upload percentage, followed by a short Verifying upload… step. Modal navigation is locked while an upload is in flight so the transfer isn’t aborted.
5
Add more or continue
On success, the file appears in the Uploaded list with a green check. Repeat for additional invoices, or click Next / Done to leave the step.
- 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.Only PDF and CSV invoices are accepted. Other file types are rejected before the upload starts.
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.
· 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.1
Create a new admin key
In the provider console, create a fresh admin key.
2
Open Configure in Dash.fi
Open the AI Spend Agent, click Configure, and select the connected provider.
3
Rotate
Click Rotate, paste the new admin key, and confirm.
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.1
Open Configure
Open the AI Spend Agent and click Configure.
2
Disconnect
Select the connected provider and click Disconnect. Confirm when prompted.
Troubleshooting
'A live connection already exists' when connecting
'A live connection already exists' when connecting
You already have an active key for that provider on your account. Use Rotate instead of Connect to replace it.
Usage or findings look empty after connecting
Usage or findings look empty after connecting
The initial sync can take a few minutes. If views are still empty after 10 minutes, click Sync now, then Refresh insights. If usage populates but findings don’t, the agent may not have detected any issues in that window.
Connection shows a Sync issue chip
Connection shows a Sync issue chip
The last background sync hit a transient failure. Dash.fi keeps retrying on the normal schedule, so the chip usually clears on its own. See Connection sync health for the full state model. If it stays in this state for more than a day, contact support@dash.fi.