Pharosdata Pharos API

Name: Pharos API
Brand: Pharos API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentAnalyticsData PipelinesapiKey2 EndpointsREST

For Agents

Submit asynchronous geospatial data queries and poll for results. The two-endpoint API handles long-running analytics jobs without blocking.

Install Jentic One Beta

Connect the Pharos API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Pharos API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Pharos API.

Submit complex geospatial data queries for asynchronous processing

Poll job status to determine when query results are ready

Process large-scale geospatial analytics without request timeouts

Retrieve computed results once async jobs complete

GET STARTED

Start building with Pharos API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Pharos API for, with concrete tasks.

★ Asynchronous Geospatial Analysis

Submit geospatial queries that require significant processing time without blocking the calling application. POST /async accepts query parameters and returns a job identifier immediately. Agents then poll GET /check with the job ID until results are ready. This pattern handles complex spatial computations, area aggregations, and multi-layer data intersections that would exceed synchronous request timeouts.

Submit a geospatial query via POST /async with area coordinates and data parameters, receive a job ID, then poll GET /check with the job ID until status shows completion

Long-Running Data Pipeline Integration

Integrate Pharos into data pipelines where geospatial enrichment or analysis steps take variable time. The async pattern allows pipeline orchestrators to submit jobs, continue with other tasks, and retrieve results when ready. This decouples the pipeline execution from the query processing time, improving throughput and resilience.

Submit a batch of geospatial queries via POST /async for each dataset partition, track all job IDs, then collect results from GET /check as each completes

AI Agent Geospatial Query via Jentic

AI agents submit and monitor geospatial data queries through Jentic without implementing async polling logic manually. Agents search for geospatial analysis capabilities, receive the two-step operation pattern (submit then check), and Jentic handles the async workflow coordination. This enables agents to incorporate geospatial intelligence into decision-making workflows.

Search Jentic for 'submit a geospatial data query', load the POST /async schema, execute with query parameters, then load GET /check and poll until results are available

Key Endpoints

2 endpoints — jentic publishes the only available openapi specification for pharos api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/async

Submit a geospatial data query

GET

/check

Check query completion status

POST

/async

Submit a geospatial data query

GET

/check

Check query completion status

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Pharos API keys (X-API-Key header) are stored encrypted in the Jentic vault. Agents receive scoped access without the raw API key entering their working context.

Intent-based discovery

Agents search by intent (e.g., 'submit a geospatial data query') and Jentic returns the two-step Pharos operation pattern (submit via POST /async, poll via GET /check) with typed schemas.

Time to first call

Direct Pharos integration: under 1 day for the simple two-endpoint pattern. Through Jentic: minutes — search, load schemas for both endpoints, execute the async workflow.

FAQs

Specific to using Pharos API through Jentic.

Why is there no official OpenAPI spec for Pharos API?

Pharos Data does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Pharos API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

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.