Developer platform
Corollary from your own code
The same research agent that answers in the app — every model, tool, database and pipeline it can reach — behind an HTTP API your software calls with a key. A key belongs to your account and spends its credits: the 30,000 a month a free account gets, with nothing separate to set up or fund.
A first request
Make a key on the API keys page, then ask the API who it thinks you are. This call is free.
curl https://corollary-labs.com/api/v1/me \
-H "Authorization: Bearer $COROLLARY_API_KEY"The answer names the key, the plan and what is left to spend:
{
"object": "account",
"key": { "id": "0f40ebe7-…", "name": "analysis-server" },
"plan": { "id": "free", "name": "Free", "monthly_credits": 30000 },
"credits": { "available": 28410, "reserved": 0 }
}What is here
All pages
Get started
Guides
- AuthenticationHow a request says who it is, and how to keep a key safe.
- Credits and limitsWhat the API spends, from which balance, and how fast you may call it.
- ErrorsOne error shape, and what each type means for your code.
- Research runsAsk a question, follow the run, answer its questions, fetch its files.
- MCP serverConnect Claude, ChatGPT or Cursor to the catalogue of models, tools and databases.
Reference
- AccountGET /api/v1/me — the key, the plan and the credits left.
- ModelsDescribe and run any model directly: POST /api/v1/models/{id}/runs.
- RunsCreate, read, stream, answer and cancel a research run.
- ThreadsList, read and delete the conversations runs belong to.
- FilesGET /api/v1/files/{id} — structures, figures, tables and pages a run made.
What is coming
Hosted views — a URL for any tool result that renders it the way the app does, a rotatable structure or a chart, for embedding in your own pages — and webhooks for run completion are next. The endpoints on this site are the ones that exist today; nothing is documented ahead of shipping. The base URL is https://corollary-labs.com/api/v1.
