Kelly Developers
Copy page
Build on Kelly's fantasy and betting numbers through the Kelly API, the Kelly Wire stream and, when it opens, the MCP server.
Kelly answers fantasy and betting questions with numbers its engine computes, and every number carries its provenance: who produced it and when it was true. These docs cover the three ways to build on it.
Kelly is in a staff-gated beta. API keys go to Kelly staff only, and nothing is charged during the beta. Some operations need no key at all, so anyone can make a first call.
Start hereLink to this section
- Authentication: keys, scopes and who can get one.
- Conventions: versions, IDs, times, paging and the headers every response carries.
- API reference: every operation and every Kelly Wire topic, generated from the definitions.
What answers todayLink to this section
| Operation | Access | Status |
|---|---|---|
GET /health | public | live |
GET /v1/status | public | live |
GET /v1/reference | public | live |
GET /v1/reference/{topic_id} | public | live |
POST /v1/wire/tickets | public | live |
GET /v1/stream/{topic} | public | live |
POST /v1/answers | run:answers | live |
The status column comes from the definition's x-status field. Until that field is filled in (planned, P8, October 16, 2026), every operation reads "unmarked".
Choose how you buildLink to this section
- REST API at
api.askkelly.ai: one call per question. See the API reference. - Kelly Wire at
wss://wire.askkelly.ai/v1: live values pushed as they change. See streaming. - MCP server at
https://mcp.askkelly.ai/mcp: Kelly's tools inside an AI client. The server is planned and doesn't run yet (P8, October 16, 2026); see MCP server.