The Key Vault
The vault is where provider API keys live — encrypted at rest, organized by brand, and usable by every request that needs that provider. It's the answer to keys scattered across .env files. You manage it on the Vault tab at /dashboard/gate/vault.
Everything on this page is also readable by an agent or a script: Your Subscriptions is the machine-readable projection of the same keys, with entitlement and free lease slots per subscription.
Your keys, your connected companies, and the shared pool
A workspace is served only on keys it may use, tried in this order:
Your own keys — the keys in your vault. They always go first, so your quota and billing are used first.
Your connected companies' keys — keys a company you have connected under Connected companies has not marked Keep private. See Share keys between the companies you run.
The shared pool — free-tier keys other workspaces chose to lend. Your workspace draws on it only while it lends at least one active free key of its own.
A workspace with no key it may use is refused with no_access, naming the providers that would unlock the model and a link to setup. The gateway never falls back to someone else's key.
The Share with SpiderIQ key pool switch under Routing is on for a new free key: your free key is shared with the pool, so other workspaces can use its free quota. Turn the switch off to keep it private. The provider's terms may forbid sharing, so it is your call. Only a brand admin can change the switch; other members see it read-only. Paid and subscription keys start private, and a metered key never pools, whatever the switch shows. Keys added before this default stay as they were.
Adding a key
On the Vault tab, click Add Provider, pick a provider from its group (subscriptions, free keys, pay-as-you-go, enterprise, media, other tools), and paste your key. When you click Add key, SpiderGate checks the key with the provider before it stores anything; a key the provider refuses is not saved. The dialog's Need help? Get a key from … link opens the provider's own key page.
For step-by-step instructions per provider — where to get the key, what its free tier and terms allow, and what the check does — see the provider guides in the sidebar, for example Groq, OpenAI or MiniMax. To point an agent tool at SpiderGate, see the agent guides, such as n8n.
Keys are encrypted with Fernet symmetric encryption before they're stored; SpiderGate keeps only a masked preview (e.g. sk-o…xyz) for display.
Inviting a contributor
Sometimes the person who owns a key isn't the admin. The Invite Contributor flow handles that without anyone sharing a raw secret:
From the Vault, send an invite (email + provider + an optional message). SpiderGate emails a signed link, valid for 72 hours.
The contributor opens the link, lands on a public page (no login required), and either pastes their API key or completes an OAuth sign-in in their own browser.
The encrypted credential lands in your vault. The admin never sees the contributor's raw key.
This is also how you add keys for providers that use OAuth rather than a pasted key.
Re-authenticating a key
When an OAuth credential stops working (for example, a refresh token is revoked), SpiderGate auto-disables it after repeated failures and emails the contributor a re-authentication link, valid for 120 hours. They re-login or paste a fresh key, and the existing vault entry is updated in place — same key id, same sharing and limits, history preserved — and the engine hot-reloads so it works again without a restart. Each vault key card also has a Re-authenticate action you can trigger manually.
If a re-authentication link has expired by the time the contributor clicks it, the expired-link page now offers a Request a new link button — a self-service way to have a fresh link emailed without waiting for an admin. (The 120-hour validity is set to outlast the full reminder cycle, so this is a fallback rather than the common path.)
Note: The multi-modal endpoints (images, audio, embeddings) require an OpenAI key in the vault. Until one is registered, those calls return
503with codeno_openai_key. Add ansk-…key via the contributor invite flow. See Images, Audio & Embeddings.
What each key shows
Open any key on the Vault tab to see its full detail — the vault is a secret-manager, not just a key list:
Quotas — how much of the key's budget you've used, per key: requests today / this minute / this hour, and tokens today / this month. Set a limit and the meter fills as you spend against it.
Subscription — for a subscription-plan key (e.g. a flat-rate coding plan), a window meter shows how much of the current billing window you've consumed and when it resets.
Balance — for providers that expose a billing API (OpenRouter, fal.ai, KIE, WaveSpeed), the key card shows the live provider balance and recent usage, with a Sync action to refresh it.
Usage policy — control which activities a key is allowed to serve. Where a provider's Terms of Service restrict a use (for example, a coding-plan key that may not be used for batch jobs), the matching toggles are disabled with the reason shown, so you can't accidentally configure a key against its provider's terms.
Metadata — a friendly label, notes, tags, who added the key, and when it was last rotated — so a shared vault stays organised.
An account password, if one is stored for a provider account, is never shown in the normal view — it's revealed only to a super-admin, on demand, and is never cached in your browser.
Health and rotation
Every key's health is tracked. After repeated failures a key is marked unhealthy and skipped during routing. Adding multiple keys per provider lets SpiderGate rotate across them — exhausting each free tier before moving on.
Next steps
Mint tokens that use these keys — Agent Keys.
See which providers are configured — Models & Direct Routing.
Add an OpenAI key to unlock Images, Audio & Embeddings.