Use your own AI key
Run EQUIRE's AI on your organization's own Anthropic or OpenAI API key.
By default, EQUIRE pays for the AI it runs for you. An organization admin can instead save your organization's own API key from Anthropic (Claude) or OpenAI (ChatGPT). EQUIRE then runs AI requests on that key, and your provider bills your API account for them.
Own-key access is turned on for each organization. If the Provider keys card says it is not on for yours, contact us.
An API key, a login and the connector
These are three different things:
- An API key comes from your Anthropic or OpenAI API account. It is not your Claude or ChatGPT login.
- Your Claude or ChatGPT login is your chat subscription. EQUIRE cannot use a login in place of an API key.
- The EQUIRE connector lets you use EQUIRE from Claude or ChatGPT. It does not pay for EQUIRE's AI and it is not an API key. See Connect an AI Assistant.
Get a key
- Create an API key with Claude or ChatGPT (OpenAI).
- Eligible Claude and ChatGPT subscriptions include monthly API credits you can use here. Claim them in your provider account, then create an API key: Claim Claude subscriber credits, Claim ChatGPT subscriber credits.
- To add credit later: Add credit with Anthropic, Add credit with OpenAI.
Add the key
An organization admin opens Settings, AI Settings, Provider keys, picks the provider and saves the key.
- EQUIRE first asks the provider whether it accepts the key. If the provider does not, nothing is saved and the card says so, for example "Anthropic did not accept this key. Check the key and try again."
- If the provider could not confirm the key, it is saved and the card shows "Could not verify".
- A key the provider accepts but refuses to serve from EQUIRE, such as one limited to certain IP addresses, is not saved.
- EQUIRE checks saved keys again each day and shows the result on the card.
- The card never shows a saved key again. It shows the provider and the last four characters.
Only organization admins can add, turn off or remove a key.
Strict key mode
Strict key mode decides what happens when your key cannot serve a request.
- Off: if your key fails, a request can fall back to EQUIRE's key. Calls that land on EQUIRE's key, including a fallback after your key fails, are billable.
- On: your key serves text AI. If the key fails, runs out of credit or reaches a spending limit, those requests fail and are not retried on EQUIRE's key. A model your provider cannot serve is refused.
To turn strict key mode on, your organization needs own-key access and a working key. Turning it off is always possible. In strict key mode, text requests on your key skip the Vercel AI Gateway. For what that changes in how your data is handled, see Subprocessors & AI.
When a request fails in strict key mode, EQUIRE says why and what an admin can do. For example: "Anthropic rejected your organization's key. EQUIRE did not use its own key because strict key mode is on. An admin can update or replace the key in Settings." When the provider is only limiting requests, wait a moment and try again. When a key is rejected or out of credit, admins also see a notice at the top of EQUIRE.
What still runs on EQUIRE's key
Some features always use EQUIRE's own accounts, whatever your settings: reading scanned PDFs, live voice, short text judgment checks such as what a spreadsheet cell means, and web pages and search from services such as Firecrawl and Exa.
Features your provider has no model for, such as embeddings on an Anthropic key, images and speech, run on EQUIRE's key. In strict key mode an admin chooses: with Allow EQUIRE's key for features your provider lacks on, web search, search ranking, images, image checks, speech, transcription and, without an OpenAI key, embeddings use EQUIRE's key and are billable. With it off, those features are refused.
Who pays
- Requests on your key: your provider bills your API account.
- Requests on EQUIRE's key: billable to your organization.
- The own-key plan needs strict key mode and a working key. It includes only a small EQUIRE-paid AI allowance.
Turn it off
An admin can turn strict key mode off, turn a key off or remove it at any time. With strict key mode on, removing or turning off the last working key stops text AI until a key is added, and EQUIRE asks first. On the own-key plan, with strict key mode off, a missing, rejected or rate limited key falls back to EQUIRE's key and uses the plan's small allowance. When the allowance is used up, all AI pauses until the next period.
Last updated on