DEVELOPERS

Build on One Move.

One Move has a public, versioned REST API for chess and poker reports, two Streamable HTTP MCP servers, and machine-readable discovery documents. Public reads need no key.

Start here

• REST API reference: versioning, authentication, endpoints, pagination, async jobs, idempotency, rate limits and errors.
• MCP servers: the product server, the documentation server, server cards and tools.
• auth.md: the WorkOS auth.md walkthrough for agents.
• Developer portal: quickstart, self-serve OAuth clients, sandbox and support.
• Sandbox: a stable synthetic report for schema and retry tests.
• OpenAPI 3.1 description.
• llms.txt and agents.md.

Base URLs

First request

curl -sS https://api.getonemove.app/v1/constraints
curl -sS "https://api.getonemove.app/v1/free-reports/chesscom/hikaru?time_class=blitz"

A report is either ready immediately with HTTP 200, or queued with HTTP 202 and a status_url. Poll the job URL until it is done, then read result_url.

What is public

Public read endpoints require no key. They return public chess usernames' reports and the Constraint catalog. They never read a private player account. Write endpoints create a report request or an OAuth client and are rate limited.

Versioning and deprecation

The stable surface is /v1. Breaking changes go to /v2. Additive fields may appear in /v1 responses. Deprecated endpoints carry Deprecation and Sunset headers and stay available for at least 90 days.

Rate limits

Every response carries RateLimit-Limit, RateLimit-Remaining, RateLimit-Reset and RateLimit-Policy. A 429 carries Retry-After. The default budget is 120 requests per minute per IP; report creation has a separate, stricter budget.

Source and issues

The source, agent instructions and issue tracker are at https://github.com/chrissuperduper/one-move-agent.