Operational

API Keys

Keys authenticate every request to the gateway. Give each environment its own key so usage and revocation stay separable.

Key management docs
Active keys3
Revoked keys1
Requests299,593lifetime across keys
Default endpointapi.prbycode.com/v1

Issued keys

Revoked keys stop authenticating immediately. Rotation issues a new value under the same name.

NameKeyRequestsCreatedLast usedStatus
ProductionFull accessprby_••••••••••4f92184,203Jun 14, 20262 minutes agoActive
StagingInference onlyprby_••••••••••8c1720,418Jul 02, 20264 hours agoActive
Analytics readerRead onlyprby_••••••••••1a633,092Aug 11, 2026YesterdayActive
Legacy workerFull accessprby_••••••••••77de91,880Feb 28, 2026Mar 19, 2026Revoked
  • ProductionActiveprby_••••••••••4f92 · Full access · 2 minutes ago
  • StagingActiveprby_••••••••••8c17 · Inference only · 4 hours ago
  • Analytics readerActiveprby_••••••••••1a63 · Read only · Yesterday
  • Legacy workerRevokedprby_••••••••••77de · Full access · Mar 19, 2026

Using a key

Send the key as a bearer token. Never expose it in client-side code.

Request headers
curl https://api.prbycode.com/v1/chat/completions \
  -H "Authorization: Bearer $PRBYCODE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "model": "glm-5.3-flash", "messages": [{ "role": "user", "content": "Hello" }] }'