Can I find the stops nearest a location with the De Lijn API?

Yes. The nearby-stops endpoint takes a set of coordinates and returns the stops around that point, and you can then read the lines serving those stops and their timetables. You can also list stops by municipality or look them up by stop key.

What are the rate limits for the De Lijn Open Data API?

The OpenAPI spec does not state rate limits, and the subscription key is managed through De Lijn's API portal. Check the official documentation at https://data.delijn.be/ for current quotas before running heavy queries.

How do I query De Lijn transit data through Jentic?

Add the De Lijn Open Data API from the Jentic API Directory and connect your subscription key once. Your agent then searches by intent such as 'stops near a location' and calls the matching operation. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Can I limit which De Lijn lookups my agent is allowed to call?

Yes. Every operation is a read-only GET, so you grant your agent only the lookups it needs, such as stops and timetables while leaving out the full network listing. The municipality and stop identifiers sit in the URL path, so a rule can also pin the agent to specific path operations, and every call is logged.

Is there a De Lijn transit MCP server?

You don't need an MCP server to give your agent De Lijn data. Jentic connects it directly from the API Directory: import it, connect your key once, and your agent can look up stops, lines, and timetables without another server loading tool definitions into its context.