HTTP API
The maplet, screen, transit and route endpoints, with parameters and examples.
Boot the API locally:
supercarto serve --port 8787
It serves GET /maplet, GET /scr, GET /transit and GET /transit-route,
each answering YAML (format=yaml) or JSON. GET /health reports the
server’s cache health.
GET /maplet
latquerynumberrequiredLatitude in [-90, 90].
lonquerynumberrequiredLongitude in [-180, 180].
radiusMqueryintegerDefault:
300Radius in metres, clamped to the machine’s limit.
budgetqueryintegerDefault:
1024Token budget for the emitted YAML.
layersquerystringComma-separated layer filter.
formatquerystringDefault:
jsonyaml returns the agent-ready document directly.GET /transit
Same parameter style: lat, lon, radiusM, budget, at
(the instant to evaluate), and format. The per-deployment feed comes from
SUPERCARTO_GTFS; a specific request can name its own feed with
?feed=<dir or zip>, and the operator’s SUPERCARTO_GTFS_RT follows feed
overrides, so a feed override never silently drops live data.
GET /transit-route
Adds fromLat, fromLon, toLat, toLon, and maxWalkM. The answer is
the certified ride plan.