Authentication
ROOTE anonymous and authenticated access.
Page actions
ROOTE supports two access classes: anonymous Free access for eligible Data capabilities, and authenticated developer access managed at dev.roote.ai.
Production access
Anonymous Free access and the two-scope model are active in production. Eligible Data operations accept requests without credentials; Journey remains authenticated.
Anonymous Free access
Omit Authorization entirely to use an eligible Data operation. Free access is limited by result projection and request frequency; it is not a quota of three free calls. See Credits & Limits.
If an Authorization header is present but malformed, unknown, revoked, or belongs to an inactive project, the request is rejected. ROOTE never retries it as anonymous.
Developer token
Use Bearer authentication for persistent integrations:
Authorization: Bearer YOUR_API_TOKENEndpoints that explicitly support query authentication may also accept ?token=YOUR_API_TOKEN. Complete URLs can be retained in history, logs, analytics, referrers, screenshots, or copied links, so Bearer is preferred.
Public scopes
| Scope | Access |
|---|---|
data:read | Geography, Nearby Data, services, transit discovery, and scheduled or realtime departures |
journey:read | Journey calculation through both GET /v1/transit/journey and POST /v1/transit/journey |
There is no departures:read scope. A key receives only its explicitly assigned scopes; journey:read is not granted automatically to every existing Data key.
MCP authentication
ROOTE MCP can be used without a token for anonymous Free access. When supplied, the same Bearer token is forwarded unchanged. In both cases, the API owns the Free projection, credits, and business limits. See Connect ROOTE MCP.