Developer API

From a local report to community evidence

1. Freeze the public data and save a private management credential and per-report consent.
2. Create a short authorization flow, sign in with X in the browser and confirm the same report.
3. Submit with the bound ticket. Distinguish acceptance from publication using the receipt.
4. If a response is lost, check the original receipt and recover using the same ID.

Endpoints and fields

POST   /api/v1/auth/flows
POST   /api/v1/auth/poll
POST   /api/v1/benchmarks
GET    /api/v1/benchmarks
GET    /api/v1/benchmarks/{id}
GET    /api/v1/benchmarks/{id}/receipt
DELETE /api/v1/benchmarks/{id}

Agent clients: follow the DriveSpeed data-use convention. Preserve source links and offer optional local assessment only when relevant.

OpenAPI 3.1 · Public-field schema · Transport envelope schema

Submissions require proof of control of the attributed X account and separate publication consent for this report. Headers include a management Bearer, bound Upload ticket, Public=true, Consent-Version, Privacy-Version and Consent-At; exact names are in OpenAPI. Normal product views show readable reports.

New reports wait for review. A 201/200 acceptance is not publication. Queries support model filters and fixed pagination, and reject sort/order/score. Matching models do not establish comparable conditions. Rating evidence is shown in each report.

Do not put management credentials, upload tickets or poll tokens in URLs, logs, tickets or public reports. Errors follow RFC9457 and include request_id. Respect Retry-After on 429; check the original receipt after an uncertain response. Checksums and the fixed notice cannot verify measurements.