Provider Keys

Use your own OpenAI, Anthropic, Azure or Amazon Bedrock account for that provider's traffic instead of DarcyIQ's

Dispatch works without any provider accounts of your own. By default, every request runs on DarcyIQ's provider accounts and is billed as part of your Dispatch spend. If your organization already has an account with a model provider, you can bring its key, and that provider's traffic runs on your account instead. Most organizations never need this tab.

Provider keys are on the Provider keys tab of the Organization page.

Which Providers

You can bring an account for:

Provider	What to paste
OpenAI	A secret key from the API keys page of your OpenAI account
Anthropic	An API key from the Anthropic Console
Azure	A JSON list of resources, even when there's only one. An AI Foundry resource covers every model in it; an Azure OpenAI resource needs an entry for each deployment.
Amazon Bedrock	A long-term API key from the AWS console, under Amazon Bedrock. It's tied to the region you create it in, and the identity behind it needs bedrock:InvokeModel and bedrock:InvokeModelWithResponseStream.

For Azure, each entry needs an api_key, plus either a resource_name for an AI Foundry resource or an endpoint_url for a single Azure OpenAI deployment. If you set resource_type, it must be ai_foundry or openai. The field shows an example to start from.

What Changes When You Add One

• Who pays for that provider's requests. A key you add takes precedence over DarcyIQ's for the same provider as soon as it's added, and keeps it from then on. Requests that reach that provider run on your account.

• Only that provider. Precedence is per provider. An OpenAI key decides who pays for requests that reach OpenAI; it doesn't affect any other provider.

• Data residency. If you've restricted data residency, requests through your own provider keys follow your agreement with that provider.

Adding a Key

1

Click Bring a key The Bring a provider key panel opens.

2

Choose the provider Pick from Provider. The credential field changes shape to match: a masked field for a key, or a larger box for Azure's JSON.

3

Paste the credential Dispatch checks its shape before saving, for example that an Azure configuration is a list, or that a key hasn't been pasted as JSON. It can't check whether the key is live, so a key that's wrong in other ways shows up as failed requests.

4

Name it (optional) and click Add key A name helps tell two keys for the same provider apart, such as a team or an account. Leave it blank and it's called, for example, "OpenAI (customer)". That provider's traffic runs on your account from the next request.

A provider key can never be read again, by you or by DarcyIQ. Afterwards, Dispatch shows only its last few characters. If you need to change it, rotate it.

Managing Keys

The table shows each key's Provider, Name, the last characters of the Key, and whether it's Active.

Action	What happens
Active switch	Pauses or resumes the key. While it's paused, that provider's traffic goes back to DarcyIQ's account, and you don't have to paste the key again to resume.
Rotate (circular arrow icon)	Replaces the credential in place. Paste the new one and click Rotate key. The key keeps its name and its place ahead of DarcyIQ's account; only the credential changes.
Remove (bin icon)	That provider's traffic returns to DarcyIQ's account, billed as part of your Dispatch spend. Nothing stops working. The key can't be restored, so pause it instead if the change is temporary.

Next Steps

Goal	Documentation
Restrict where requests are processed	Data Residency
See your spend by model tier	Cost Reporting
Add credits and set the organization budget	Billing & Budget