Di-Atomic Global Docs
Docs β€Ί Authentication

Authentication

SpiderGate authenticates every request with a Bearer API key. There are no other credentials β€” one key routes across all providers.

The header

Send your key in the Authorization header:

Authorization: Bearer <YOUR_API_KEY>
curl https://spideriq.ai/api/gate/v1/chat/completions \
  -H "Authorization: Bearer $SPIDERGATE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "model": "spideriq/fast", "messages": [{ "role": "user", "content": "ping" }] }'

Keep keys out of code

  • Use an environment variable (SPIDERGATE_API_KEY), never a hard-coded string.

  • Never ship a key to the browser. Call SpiderGate from your server; proxy client requests.

  • Rotate if a key leaks β€” old keys stop working immediately.

Verify a key

A quick health probe that doesn't spend tokens:

curl https://spideriq.ai/api/gate/v1/health
# β†’ { "status": "healthy", "service": "spidergate", "version": "2.70.0" }

If a completion returns 401 invalid_api_key, the key is missing, malformed, or rotated β€” see Errors.

Last updated July 19, 2026