How do I get a PAT?
Free for all Colosseum Arena members. Log in to Colosseum Arena and generate a token. Set two environment variables:Which tools are supported?
| Tool | Status | Install method |
|---|---|---|
| Claude Code | Supported | npx skills add ColosseumOrg/colosseum-copilot |
| Codex | Supported | npx skills add ColosseumOrg/colosseum-copilot |
| OpenClaw | Supported | npx skills add ColosseumOrg/colosseum-copilot -a openclaw |
What are the rate limits?
See API Reference for the full rate limit table.What happens when my idea already exists?
Copilot tells you directly. It runs incumbent validation and classifies the gap:- Full gap: the incumbent hasn’t addressed the problem
- Partial gap: incomplete coverage (segment, UX, geographic, pricing, or integration)
- False gap: already solved
Is my research data private?
Yes. Copilot is a stateless API. Queries and results are not stored, shared, or used for training.How current is the data?
- Hackathon projects update after each Colosseum hackathon
- Archive sources refresh on varying intervals (protocol docs within days, historical archives are static)
- The Grid provides near-real-time on-chain product data
- Web search is live
- Breakpoint transcripts are added after each annual conference
What’s the difference between conversational and deep dive mode?
Conversational (default): Answers questions with targeted API calls and inline citations. Fast, concise, evidence-backed. Good for lookups, comparisons, and quick assessments. Deep dive (explicit opt-in): Full 8-step research workflow with parallel data gathering, incumbent validation, gap classification, and a structured report including revenue model, GTM strategy, and risk assessment. Activates when you say “vet this idea”, “deep dive”, or “should I build X?”Can I use the API directly without the skill?
Yes. The skill file is a prompt that teaches your coding assistant how to use the API effectively, but the underlying REST endpoints work with any HTTP client. See API Reference for curl examples.What if my query returns no results?
Archive search auto-cascades through three retrieval tiers (vector → chunk text → document text) before returning empty. If you still get no results:- Try conceptual synonyms (e.g.,
"prediction markets"→"futarchy") - Broaden the query (3–6 keywords work best)
- Remove filters that may be too restrictive
- Check if the topic exists in the corpus (some niche areas may not have coverage yet)