Bring your own provider keys
Found this helpful? Share it:
Found this helpful? Share it:
Connect your own provider API key and idapt routes that model straight to your account with the provider, so the usage lands on their bill instead of your idapt balance 🎛️
A provider connection stores your own key for OpenAI, Anthropic, Google, or xAI, or a custom OpenAI-compatible endpoint. When idapt runs a chat model through your key, the request goes to that provider under your contract, and you pay them directly.
Your own keys serve chat models. Image, video, speech, and transcription run on idapt's own providers and draw your plan's usage as usual, whether or not you have connected a key.
Bringing your own key is also the way to pay for models on idapt without a subscription: Usage Credits need an active plan, but your own keys work on every tier within the free-tier call caps below.
Calls made through your own key draw $0 from your idapt credits. idapt records them for your usage analytics but does not charge you for the model.
Open the AI Routing page for your workspace
Find Provider endpoints and choose Add endpoint
Pick the provider and paste your API key
Optionally set it as the default for chat models, then save
Keys are encrypted before they are stored and are only ever used server-side for provider requests. You can test, disable, or delete a connection at any time, and deleting one stops chats from using it immediately.
Connecting keys is free to set up. The limits depend on your plan:
The free plan allows 3 provider connections and 100 cloud calls through your keys every 30 days.
Subscriptions raise the connection limit and lift the monthly call cap.
Models running on a computer you have paired do not count against the connection limit.
Because a connection runs under your own provider account, requests run under your own contract and account terms with that provider, not idapt's. Your key is encrypted before storage and only ever used server-side to serve your own requests.
idapt cannot verify how that provider handles your data, so BYOK routes count as unverified under the no-training routing floor. Either turn the floor off for your BYOK traffic or record terms that confirm the endpoint does not train on requests. See Control which providers see your data.
When you add a connection, record whether the endpoint trains on requests, its retention period, and its terms URL so routing filters can take them into account.
Related articles
Control which providers see your data
Read provider data-policy labels, block providers, and restrict routing to verified no-training providers.
Choosing models
Browse 200+ AI models, read their cost bands, set the speed dial, and pick the right model for each conversation.
Your data and privacy
What idapt stores, who can see it, how AI providers handle it, and the controls that keep you in charge.
Up next
Your data is never locked in. Export chats and files in standard formats any time.
Was this helpful?