Get a Cloudflare Workers AI token
Who this is for: anyone who wants Cloudflare Workers AI models through SpiderGate on their own Cloudflare account.
What this does: walks you through creating a Workers AI API token, copying your Account ID, and adding both to your SpiderGate vault.
Before you begin
A Cloudflare account. Cloudflare says users have the Workers Free plan by default.
About 3 minutes.
Limits and terms to know first
Both the Workers Free and Workers Paid plans include "10,000 Neurons per day". On Free, once that is used, "further operations will fail with an error". Workers Paid has a minimum charge of $5 a month and bills usage above the daily allocation. Some models need Workers Paid.
Cloudflare says it "does not use Customer Content processed by Workers AI to train AI models".
Warning: Cloudflare's terms say you may not "rent, lease, loan, export, or sell access to the Services to any third party", and that giving others your API token is "at your sole risk". Keep this token to your own brand.
Steps
Step 1 — Create the token
In the Cloudflare dashboard, open Workers AI and select Use REST API. Select Create a Workers AI API Token, review the prefilled settings, then select Create API Token and Copy API Token.
Copy it straight away. Cloudflare's pages disagree on whether you can see the token again, so do not count on it.
Step 2 — Copy your Account ID
On the same page, under Get Account ID, copy the Account ID. You can also find it under Workers & Pages → Account Details.
Step 3 — Add the key in SpiderGate
Open Gate → Vault (/dashboard/gate/vault) and click Add Provider. Type Cloudflare in Search providers... and pick it from the Free keys group.
Fill in the dialog:
API Token — paste the token
Account ID — paste the Account ID
Label — a name you will recognise later, for example the account it came from.
Under Routing, turn Share with SpiderIQ key pool off. It is on by default, and while it is on, other brands can draw on this key's free quota. Your provider's terms tie the key to your account (see the warnings above), so keep it to your brand.
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 Cloudflare with the key before it stores anything: it searches the Workers AI models on your account, using the token and the Account ID together.
If Cloudflare 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 cloudflare key did not pass its check: <reason>. Nothing was saved.The reason is SpiderGate's own wording, never Cloudflare'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.
Troubleshoot
Requests fail with error 3036 and a 429. Cloudflare's message: "You have used up your daily free allocation of 10,000 neurons." It resets daily.
Requests fail with error 5035 and a 403. "This model requires a Workers Paid plan." Pick another model, or upgrade the Cloudflare account.
A custom token fails the check. If you built the token yourself instead of using the template, Cloudflare says it needs both Workers AI - Read and Workers AI - Edit.
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.