Get a Together AI key

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

What this does: walks you through buying Together credit, creating a project API key, and adding it to your SpiderGate vault.

Before you begin

A Together AI account at api.together.ai.
Credit. Together says it "does not currently offer free trials": your organisation's first purchase is at least $15, and later ones at least $5. Prepaid credit does not currently expire.
About 5 minutes.

Limits and terms to know first

Together says most use runs without rate limits, though limits "may occasionally occur with high request volumes or large bursts of traffic".

Warning: Together says that "by default, Together stores the prompts you send and the responses models return, and may use them for product improvements." Sharing data to train other models is opt-in. Check your privacy settings before you send personal data.

Warning: Together's terms forbid you to "transfer, distribute, resell, lease, license, or assign the Services". Keep this key to your own brand.

Steps

Step 1 — Buy credit

Open your organisation's billing page at api.together.ai/settings/organization/~current/billing and make your first purchase.

Step 2 — Create the key

Open the project's API keys at api.together.ai/settings/projects/~current/api-keys. Select Create API Key, enter a name, then select Create. Copy it now: Together says "It won't be shown again."

Step 3 — Add the key in SpiderGate

Open Gate → Vault (/dashboard/gate/vault) and click Add Provider. Type Together 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 Together AI with the key before it stores anything: it lists your models at https://api.together.xyz/v1/models.

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

The reason is SpiderGate's own wording, never Together AI'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 402. Together's 402 means the account "has reached its maximum allowed monthly spending limit".

Requests fail with a 429. Together limits serverless requests "during high demand". Retry after a short wait.

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.