Skip to main content
Copilot uses Personal Access Tokens (PATs) for authentication. Every API request requires a valid token.

​
Getting a Token

1

Sign in to Colosseum Arena

Go to colosseum.com/arena and sign in with your account. If you don’t have one, sign up first. Any auth method works (email, Google, GitHub).
2

Open the Copilot setup page

Navigate to colosseum.com/arena/copilot. If you’re not signed in, you’ll be redirected to the sign-up page.
3

Generate and copy your token

Click Generate your token. The token appears once — copy it immediately using the Copy button. The full token is only shown on this page.Below the token, you’ll see a ready-to-paste export snippet for your terminal. Copy that too.
4

Store it securely

Add the token to your shell profile so it persists across sessions:
Then reload your shell: source ~/.zshrc

​
Using Your Token

Pass the token as a Bearer token in the Authorization header:
If you’re using the Copilot skill (Claude Code, Codex, or OpenClaw), the skill reads COLOSSEUM_COPILOT_PAT automatically. You don’t need to set the header manually.
Test your token with a quick curl before configuring your coding assistant:
A successful response returns a JSON object with available filters (tracks, hackathons, clusters, etc.).

​
Regenerating Your Token

Tokens expire after 90 days. You can also regenerate early if needed:
  1. Go to colosseum.com/arena/copilot
  2. Click Regenerate token
  3. Confirm in the dialog. This invalidates your current token immediately
  4. Copy the new token and update your environment variables
After regenerating, any tool or script using the old token will receive 401 errors until you update it. If you suspect a token has been compromised, regenerate immediately. See API Reference for rate limits and API Reference for error codes.