What authentication does the Locu Public API use?

The API uses an API key sent in the request header (ApiKeyAuth scheme). Through Jentic the key is stored in the encrypted vault and injected at execution, never exposed to the agent's prompt or logs.

Can I search for venues by city with the Locu Public API?

Yes. Use GET /search with a query string and supported filter parameters. The response returns a list of matching venue records with id, name, and address fields you can use directly.

What are the rate limits for the Locu Public API?

The spec does not declare numeric rate limits. Treat the API as throttled and back off on HTTP 429 responses. Jentic's executor surfaces 429s to the agent so it can retry with delay.

How do I look up a venue by id through Jentic?

Run `pip install jentic`, search for 'look up a local business', load the Locu GET /locations/{id} operation, and execute it with the venue id. Jentic handles auth and returns the parsed JSON record.

Is the Locu Public API free?

Locu's public API access tiers are not declared in the spec. Check locu.app for current pricing and quota allocations before high-volume use.

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

Yes. Because you run Jentic One yourself, your own rules decide which Locu operations and credentials the agent may use. Since Locu runs against a shared location directory rather than resources your account owns, you scope by operation: grant only the calls the agent needs, such as searching locations with GET /search or fetching a single record with GET /locations/{id}. If the agent only reads data, leave out location creation via POST /locations so it can never write to the directory.