Transitapp Transit API

Can I get transit routes which are near a location with the Transit API?

Yes. Use the GET /public/nearby_routes endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Transit API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I get transit routes which are near a location through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get transit routes which are near a location'. Jentic returns the matching Transit API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Transit API have?

The Transit API exposes 16 endpoints covering public transport, shared mobility operations.

Can I limit what my agent is allowed to do with the Transit API?

Yes. Because Jentic One is self-hosted, you decide which Transit API operations your agent may call, so you can allow just the ones a workflow needs, such as GET /public/nearby_routes, GET /public/nearby_stops, or GET /public/stop_departures, and leave out trip planning or placemark lookups. The Transit API is read-only and takes locations as query parameters, so an allowed agent can fetch nearby routes and departures but cannot create or change anything. Your API key is held encrypted by your own instance and injected at call time, so the agent only ever exercises the operations you have permitted.