What authentication does the Tankerkoenig API use?

The API uses an API key passed as the apikey query parameter on every request. The key is a UUID issued by Tankerkoenig after a free request form. Through Jentic, the key is stored in the encrypted vault and injected at execution time so the agent never sees the raw value.

Can I search for gas stations by coordinates with the Tankerkoenig API?

Yes. Call GET /stations/search with lat, lng, and rad query parameters and the response includes nearby stations with their address, opening status, and current E5, E10, and diesel prices.

What are the rate limits for the Tankerkoenig API?

Tankerkoenig publishes fair-use rules on its terms page rather than fixed numeric limits in the spec. Polling individual stations more often than once every five minutes is discouraged. For dashboards or fleet tools, prefer /stations/ids for bulk lookups instead of one request per station.

Is the Tankerkoenig API free?

Yes. The data is published under a Creative Commons licence and the API is free to use, including for commercial projects, provided attribution requirements in the licence are met.

How do I find the cheapest diesel near a user with Tankerkoenig through Jentic?

Install Jentic with pip install jentic, then run an async search for 'find cheapest diesel near coordinates'. Jentic returns the GET /stations/search operation; load its schema and execute with the user's lat, lng, rad, and type=diesel. Jentic attaches the apikey from the vault automatically.

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

Yes. Because you run Jentic One yourself, your own rules decide which Tankerkoenig operations and credentials the agent may use. You can allow only the read operations it needs, such as searching stations by coordinates (GET /stations/search), looking up a postal code (GET /stations/postalcode), bulk price lookups by station ID (GET /stations/ids), or reading aggregate statistics (GET /stats), while keeping the write operation that files a price complaint (POST /complaint) out of the agent's reach unless you explicitly include it. Since the API takes coordinates, postal codes, and station IDs as query inputs rather than URL resource IDs, scoping is done at the operation level for the exact endpoints you approve.