Can I getlocations with the API Locations?

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

What are the rate limits for the API Locations?

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 getlocations through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'getlocations'. Jentic returns the matching API Locations operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the API Locations have?

The API Locations exposes 3 endpoints covering location summary, location detail, geocode operations.

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

Yes. Because you self-host Jentic One, your own rules decide which API Locations operations and credentials the agent may use. Since the location id sits in the URL path (GET /v2/locations/{locationId}), you can pin the agent to a single location so it reads that one and nothing else. You also choose which operations it may call, so listing every location via GET /v2/locations or geocoding an address via the geocode endpoint stays off limits unless you add it.