Credits & Limits
ROOTE Free projection, credits, refunds, and request limits.
Page actions
Anonymous Free policy
Free Data requests use no account and consume zero credits. They return at most three results per category, not three free API calls.
| Family | Free category |
|---|---|
| Mobility | station, bicycle, scooter, moped, or car |
| Services | Requested canonical service_type |
| Transit nearby | First requested canonical mode advertised by the station |
| Departures | Canonical line ID, then line name, then mode as fallback |
| Geocode and place search | The operation is one category: up to three candidates |
| Reverse geocode | At most one result |
Projection happens after filters, spatial sorting, normalization, and deduplication. A smaller limit can reduce results but cannot raise the per-category cap. Anonymous Mobility forces offset=0; Global Nearby has no offset. These rules prevent pagination from enumerating beyond the Free projection.
Frequency and execution limits
- Anonymous public identity: 120 requests/minute and 2,000/hour.
- The limiter is process-local; it is not a guaranteed global quota across multiple replicas.
- Cache hits still pass access and frequency checks.
- Up to 150 new nearby acquisitions can run concurrently; cached or already shared work may still be served.
- Mobility radius is clamped to 400 m, Transit to 5,000 m, and Services to 10,000 m.
- Provider-specific concurrency, request budgets, timeouts, and circuit breakers also apply.
Behind MCP, the API sees the MCP server's egress rather than a trustworthy end-user identity, so the anonymous API budget is aggregated for MCP traffic. The MCP also applies its own edge protection.
Authenticated credits
| Operation | Current backend rule |
|---|---|
| Direct Data, departures, Journey, and geography operations | 1 credit per successful logical call |
| Global Nearby | 1 credit reserved per requested family: Mobility, Transit, Services |
| Anonymous Free | 0 credits |
A valid cache hit is still an API use and remains billable for authenticated projects. Empty but technically successful acquisitions are also settled. A total technical failure is refunded. In Global Nearby, a family that totally fails is refunded independently while successful families remain charged.
No commercial price inferred
Credits are the backend accounting unit. This page does not invent a currency price, subscription entitlement, or SLA that is not present in the backend contract.
The anonymous policy, authenticated accounting, and refund behavior described above are the active backend rules.