ProChoice API & Agent Documentation
Public, unauthenticated, read-only JSON and Markdown interfaces for ProChoice LLM and coding agent harness rankings.
REST API v1 endpoints
All API routes are public, require no API key or OAuth token, and serve read-only benchmark data compiled daily from 18 public sources under CC BY 4.0.
| Endpoint | Media type | Description |
|---|---|---|
| GET /api/v1/snapshot | application/json | Full snapshot across all 6 domains, 25 controlled harnesses, source health, and 45 lifecycle audits. |
| GET /api/v1/domains/{domain} | application/json | Headline picks and Pareto frontier for coding, writing, design, research, cyber, or harnesses. |
| GET /openapi.json | application/openapi+json | OpenAPI 3.1.0 schema covering every response and RFC 9457 error payload. |
| GET /.well-known/api-catalog | application/linkset+json | RFC 9727 machine-readable API discovery linkset. |
Quickstart examples
# Fetch the Coding Pareto frontier as typed JSON curl -sS https://prochoice.industries/api/v1/domains/coding # Request clean Markdown directly on any leaderboard page curl -sS -H "Accept: text/markdown" https://prochoice.industries/coding # Read the concise agent directory or full Markdown compendium curl -sS https://prochoice.industries/llms.txt curl -sS https://prochoice.industries/llms-full.txt
Markdown content negotiation
Every public route supports HTTP content negotiation via Accept: text/markdown. Negotiated responses return Content-Type: text/markdown; charset=utf-8 with Vary: Accept and an approximate token count in X-Markdown-Tokens. Direct static aliases are also available at /coding.md through /harnesses.md.
Versioning, deprecation, and rate limits
Stable REST endpoints are versioned in the URL path under /api/v1/. Breaking response changes require a new major version path such as /api/v2/, and any deprecated route announces retirement in advance through RFC 9745 Deprecation and Sunset headers.
Responses publish IETF RateLimit-Policy and RateLimit headers (120 requests per 60 seconds per IP) plus strong ETag headers so clients can poll with If-None-Match for zero-byte 304 responses.
Error model
Every API error returns RFC 9457 application/problem+json with status, code, title, detail, and a concrete resolution hint. Non-GET methods return HTTP 405 with an Allow: GET, HEAD header.