DEVELOPER DOCUMENTATION

Quickstart

From an idea to your first completion. One key, one compatible API.

1. Create a key

Connect your wallet, open API Keys, and sign the key-management challenge. Copy the key when it appears; it is shown once. Keep it in a server environment variable.

2. Choose an available model

Browse models available on your router. Use the exact gateway model ID. A public market listing does not guarantee an executable route on your network.

3. Make a request

Set your client’s base URL to the selected gateway’s /v1 endpoint. Paid requests use your Compute Credits; the gateway verifies balance before dispatch.

curl 'https://gpu-router-accounts-production.up.railway.app/v1/chat/completions' \
  -H "Authorization: Bearer $GPU_ROUTER_API_KEY" \
  -H 'Content-Type: application/json' \
  --data-binary '{
  "model": "your-model-id",
  "messages": [
    {
      "role": "user",
      "content": "Hello!"
    }
  ],
  "max_tokens": 256
}'

4. Inspect the result

Response headers identify the serving provider and reservation. Open Activity for token counts, cost, outcome, and latency. Or try a model in the side playground.

Ask the docs assistant

Get AI help with integration, pricing, routing, batches, latency, and privacy, with links to the relevant documentation. The assistant can explain and suggest code; it has no account access and cannot execute requests or change settings.

Try three guest questions per browser session each UTC day. Sign in with a wallet for ten questions per UTC hour, up to thirty per day. Signing a message does not authorize transactions or spend your Compute Credits. A ten-second cooldown and shared usage limits also apply. Questions go to the configured AI provider; don’t include secrets, and check the source links for accuracy.