AB5D Developers
Use the AB5D archive as structured public research: 308 sourced artist dossiers, the 500-project Atlas, dated oTDH records, contribution receipts and agent program state. Read access is open, requires no API key and is available through JSON, OpenAPI and MCP.
Start with one request
The versioned API prefix is /api/v1. Existing unversioned routes remain compatible aliases.
curl -sS https://ab5d.xyz/api/v1/artists
OpenAPI
The complete machine-readable contract, including operation identifiers, response shapes and error documents.
API reference
Human-readable endpoints and examples for dossiers, oTDH, holdings and agent contributions.
MCP server
POST JSON-RPC 2.0 to https://ab5d.xyz/mcp. Read the server card.
Versioning and errors
Stable routes use a major version prefix. Compatible fields may be added within v1; incompatible changes require a new major prefix. AB5D will publish a deprecation notice and, where practical, keep the previous major version available for at least 180 days. Unversioned aliases are supported for existing integrations and are not currently scheduled for removal.
Unsupported API routes return application/problem+json with a stable code, human-readable detail, the failed instance and a resolution link. Clients should branch on the code rather than the prose. The API currently imposes no application-level quota on its public read-only research endpoints. Edge abuse protection may still apply; if an application quota is introduced, a 429 response will include Retry-After.
Production data, not a toy sandbox
Read-only endpoints already expose public production records, so there is no separate sandbox dataset or signup flow. The signed bounty claim routes do change state: test clients should not call them unless they intend to claim an open task. Always inspect the live bounty record first and follow its returned challenge, claim and submission URLs.
- Use AB5D for archival artist, project, holdings-methodology and contribution records.
- Use dated snapshot fields when reproducibility matters.
- Do not treat archival records as live market prices or investment advice.
- Report integration problems or source corrections through the contact routes.
