Get a Replicate token

Who this is for: anyone who wants Replicate's models through SpiderGate on their own Replicate account.

What this does: walks you through finding or creating an r8_ API token, buying credit, and adding the token to your SpiderGate vault.

Before you begin

A Replicate account. Replicate's terms say you must sign in with your GitHub account.
Prepaid credit. Replicate says "you must first purchase credit upfront". Purchased credit is valid for 1 year and is not refundable.
About 5 minutes.

Limits and terms to know first

You can create predictions at 600 requests a minute. If you were granted credit and have no payment method on file, Replicate limits you to 1 request per second and at most 6 a minute.

Warning: Replicate's terms say you may not "share or disclose Login Credentials" (which include security tokens) beyond the user they were made for, or make the Services available to any other person. Keep this token to your own brand.

Steps

Step 1 — Buy credit

In Replicate's billing settings, add a payment method, then click Add credit.

Step 2 — Copy or create a token

Open replicate.com/account/api-tokens. Replicate creates a default token with your account; you can also create one just for SpiderGate and name it. Tokens are 40 characters and start with r8_.

Step 3 — Add the key in SpiderGate

Open Gate → Vault (/dashboard/gate/vault) and click Add Provider. Type Replicate in Search providers... and pick it from the Pay-as-you-go group.

Fill in the dialog:

API Token — paste the r8_ token
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 Replicate with the key before it stores anything: it reads your account at https://api.replicate.com/v1/account.

If Replicate 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 replicate key did not pass its check: <reason>. Nothing was saved.

The reason is SpiderGate's own wording, never Replicate'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 429 such as "Request was throttled". You hit Replicate's rate limit. Without a payment method you get at most 6 requests a minute.

You want to stop a token. Replicate disables tokens rather than deleting them: click the disable button next to the token on the API tokens page.

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.