What authentication does the Pharos API use?

The Pharos API uses an API key passed in the X-API-Key request header. Through Jentic, your API key is stored encrypted in the credential vault and agents receive scoped access without the raw key entering their context.

How does the async query pattern work?

POST /async submits a geospatial query and immediately returns a job ID without waiting for results. GET /check accepts the job ID and returns the current status. Poll GET /check until the status indicates completion, then retrieve the results from the response body. This handles long-running queries without timeout issues.

How do I submit a geospatial query through Jentic?

Search Jentic for 'submit a geospatial data query' to discover the POST /async operation. Load the schema to see required parameters (coordinates, data layers, query type), then execute. Use GET /check with the returned job ID to monitor progress and retrieve results.

What happens if a query fails or times out?

GET /check returns the current job status including failure states. If a query fails, the status response includes error information. There is no server-side timeout on the async processing - jobs run to completion or failure, and you poll at your own pace.

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

Yes. Because you run Jentic One yourself, your own rules decide which Pharos operations and credentials the agent can use, and the Pharos API has just two operations: POST /async to submit a geospatial query and GET /check to poll its status. Since the query target travels in the request or query rather than the URL path, the honest control here is operations-level: you can allow the agent to submit queries and check status, or restrict it to only checking status. Your stored API key is injected at execution time for the operations you permit and never enters the agent's prompt or context.