Authentication
ROOTE developer authentication and access.
Page actions
ROOTE developer access is managed at dev.roote.ai.
One developer token
The target access model uses one ROOTE developer token across the REST API and authenticated ROOTE MCP access.
Bearer authentication
Use Bearer authentication for persistent integrations:
Authorization: Bearer YOUR_API_TOKENQuery-token authentication
API endpoints that explicitly support query authentication accept:
?token=YOUR_API_TOKENQuery-token authentication is not inherently invalid. Complete URLs may be retained in history, logs, analytics, referrers, screenshots, or copied links. Prefer Bearer for persistent integrations and use query tokens only where the endpoint contract and exposure model are appropriate.
Scopes
| Scope | Access |
|---|---|
geography:read | Geography capabilities such as geocoding and place search |
mobility:read | Shared mobility and urban-service capabilities |
MCP authentication state
The target MCP model uses the same ROOTE developer token:
Authorization: Bearer YOUR_API_TOKENCurrent deployment
The currently deployed public MCP server may still accept unauthenticated clients until token enforcement is deployed. OAuth is not required by the current public setup.
See API Authentication and Connect ROOTE MCP.