TokenRoster
DevelopersTokenRoster

The TokenRoster API.

A public, read-only REST API for the TokenRoster registry — companies, DAOs, nonprofits, tokens, people, and assessment programs. No API key, no authentication, no rate-limit paperwork.

Getting startedOne curl away

The base URL is https://tokenroster.com. Every endpoint is an unauthenticated GET returning JSON in a { data, pagination? } envelope. The full machine-readable contract lives at /openapi.json.

curl "https://tokenroster.com/api/v1/companies?page=1&pageSize=5"

{
  "data": [
    { "id": "example-co", "name": "Example Co", "symbol": "EXC", ... }
  ],
  "pagination": { "page": 1, "pageSize": 5, "pageCount": 12, "total": 58 }
}
curl "https://tokenroster.com/api/v1/companies/example-co"

{
  "data": {
    "company": { "id": "example-co", "name": "Example Co", ... },
    "distribution": { ... },
    "proposals": [ ... ],
    "positions": [ ... ],
    "capTable": [ ... ]
  }
}
TokenRoster public APIv1 endpoint reference
GET /api/v1/companies
List companies. All reviewed companies, newest first. Query params: page (default 1), pageSize (1–100, default 25).
GET /api/v1/companies/{slug}
Company detail. One company with its token distribution, governance proposals, team positions, and cap table.
GET /api/v1/people
List people. Founder and contributor profiles, newest first, with each person’s reviewed-company count. Query params: page, pageSize.
GET /api/v1/people/{slug}
Person detail. One person profile with their positions at reviewed companies.
GET /api/v1/programs
List programs. Assessment programs currently open for applications, with the company running each one.
GET /api/v1/stats
Registry stats. Aggregate registry statistics: company count, open funding rounds, combined treasury, people, live programs.
AuthenticationNone required

The v1 API is read-only and serves only public registry data, so it requires no credentials of any kind. Write access — creating and managing listings — currently happens through the TokenRoster web app, and OAuth 2.0 for API clients is planned to ship alongside a write API. An MCP (Model Context Protocol) server for AI agents is also on the roadmap.

Found a gap in the docs or need an endpoint that isn’t here yet? Get in touch.