ROOTE API
Credits & Limits
ROOTE API credits and request limits.
Page actions
ROOTE applies endpoint-specific request limits and credit rules at the backend.
Credit calculation
Credit calculation is performed by the ROOTE backend. Clients should not recreate accounting from response size or provider count.
Pricing is not inferred
Where a credit cost, quota window, or price is not explicitly specified, it remains unspecified.
Documented endpoint limits
| Endpoint | Documented limit |
|---|---|
| Geocode | Up to five ordered candidates |
| Reverse Geocode | Up to five ordered candidates |
| Nearby Mobility | Default 100; maximum applied 100; radius maximum applied 400 m |
| Nearby Services | Default 50; aggregate maximum 200; radius maximum 10 km |
| Google-backed service category | Maximum 20 results per category |
| InPost lockers | Maximum 100 lockers |
Nearby responses expose requested and applied limits where documented. Rate-limit failures use rate_limited where applicable. Consult each capability page; REST and MCP limits are not assumed to be identical.