📖 Endpoint Reference

Every endpoint shares the same conventions. Learn them once and they hold across the whole API.

Conventions

• Base URL. https://api.compass.mesa.so
• Version. Data endpoints live under /v1. Every response carries a Compass-API-Version header naming the build of the plane that served it. It is additive semver: new fields raise the minor, so >= 1.2.0 tells you ticker, chains, discordUrl, linkedinUrl and slug are populated rather than absent.
• This table is not the reference of record. GET /v1/me returns the same list, generated from the price table that bills you, so it can never quote a price it does not charge. It is free. Read it from there and you are never reading a stale page.
• Auth. Every request carries Authorization: Bearer ck_live_…. See Authentication & API Keys.
• Format. Requests and responses are JSON.
• Errors. Failures return { "error": "..." } with a standard status code. See Errors & Status Codes.

Lists and pagination

Endpoints that return many records are paged. Pass a page query parameter and read the envelope:

{
  "data": [],
  "total": 0,
  "page": 1,
  "totalPages": 0
}

data is the page of records, total is the full count, and totalPages tells you how many pages to walk. Single-record endpoints return the record directly.

The endpoints

The live data endpoints are documented in Data Endpoints. The network graph is still planned; watch the Roadmap & Availability page.

Related

• Identity (GET /v1/me)
• Data Endpoints
• For AI Agents
• Architecture & Infrastructure