Get a Fireworks AI key
Who this is for: anyone who wants Fireworks-hosted open models through SpiderGate on their own Fireworks account.
What this does: walks you through creating a Fireworks API key, adding a payment method, and adding the key to your SpiderGate vault.
Before you begin
A Fireworks AI account.
A payment method, for anything past the starter credit. Fireworks bills by prepaid credit.
About 5 minutes.
Limits and terms to know first
New accounts get a $1 starter credit. Fireworks says that when it runs out, an account without a payment method "will be suspended until you add a payment method". Your spend tier sets your limits; adding a payment method puts you in Tier 1.
Fireworks says it keeps zero data by default for open models, and that it "will not use your Content to train our own models".
Warning: Fireworks' terms say you "will not share your password(s) and/or any other authentication credentials with anyone else", and may not "buy, sell or transfer API keys" without its consent. Keep this key to your own brand.
Steps
Step 1 — Create the key
Open app.fireworks.ai/settings/users/api-keys, click Create API key, and copy it.
Step 2 — Add the key in SpiderGate
Open Gate → Vault (/dashboard/gate/vault) and click Add Provider. Type Fireworks AI in Search providers... and pick it from the Pay-as-you-go group.
Fill in the dialog:
API Key — paste the key
Label — a name you will recognise later, for example the account it came from.
Under Routing, the Share with SpiderIQ key pool toggle does not apply to a metered key: SpiderGate never pools a key that bills per call, whatever the toggle shows. Switch it off anyway so the dialog matches what happens.
Click Add key. The button reads Saving... while SpiderGate checks the key.
Verify it worked
When you click Add key, SpiderGate sends one request to Fireworks with the key before it stores anything: it lists your models at https://api.fireworks.ai/inference/v1/models.
If Fireworks accepts the key, the dialog closes and the key appears in your vault list.
If it does not, the dialog stays open and shows:
The fireworks key did not pass its check: <reason>. Nothing was saved.The reason is SpiderGate's own wording, never Fireworks's error text. The usual ones are Invalid API key (401 Unauthorized), Access denied (403 Forbidden) and The account behind this key has no credit left (402).
To see the key serve a request, give it a slot in one of your own routing aliases and send a request to that alias. The trace shows which provider answered.
SpiderGate's check proves the key is valid. It does not prove the account has credit: a key on an empty balance can pass the check and then fail on its first real request.
Troubleshoot
Requests fail with a 412. Fireworks' 412 means "Account is suspended", usually because the starter credit ran out with no payment method. Add one.
Requests fail with a 402. The account "is not on a paid plan or has exceeded usage limits". Buy credit.
Too many keys checked for this workspace; try again in …s. SpiderGate runs at most 20 key checks per brand in any 10 minutes. Wait the number of seconds it gives, then click Add key again.
Request timed out (15s) or Could not reach … to check the key. Try again later. The provider did not answer in time. Nothing was saved. Try again in a minute.
The provider is rate-limiting us (429). Try again in a minute. The provider throttled the check itself. Wait a minute and retry.