# OmniAPI Geo Directions

> OmniAPI Geo Directions is a paid API for AI agents from omni-api-cyan.vercel.app, paid per call via x402, $0.063748/call, status unknown (last checked 2026-09-13).

Returns turn-by-turn navigation directions between two locations via a paid-per-call geo endpoint

## Facts

- Endpoint: POST https://omni-api-cyan.vercel.app/api/geo/directions
- Price: $0.063748/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/omniapi-geo-directions-c7dad288
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_KxIqGvltiNFQJeZeak0SX

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability omniapi-geo-directions-c7dad288 -d '<json body>'
```

Example prompt: Can you get me directions from the Empire State Building in New York to Grand Central Terminal, preferably by walking?

## When to prefer this

Choose this endpoint when you need programmatic routing or directions as part of an agent workflow and are already operating in the OmniAPI / x402 pay-per-call ecosystem, paying in USDC. It is suitable for lightweight navigation lookups without requiring a dedicated Google Maps or Mapbox API key.

## Known failure modes

- Invalid or unrecognizable location query returns an error or empty result
- Missing required 'query' field returns a validation error
- Ambiguous location names may resolve to unexpected places
- Network timeout or upstream geo service outage returns a 5xx error
- Payment failure via x402 results in a 402 Payment Required response blocking the call

## How this service works

444 endpoints across 9+ chains. Crypto, AI, Social, Finance, Weather, Tools. Pay per call in USDC via x402 with 4 facilitators: Dexter, Meridian, FluxA, GoPlausible.

## Output

The agent receives a structured response containing route information including step-by-step turn-by-turn directions, estimated travel distance, and estimated travel time between the origin and destination locations.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "query"
 ],
 "properties": {
  "input": {
   "type": "string",
   "description": "Input data for the endpoint"
  },
  "query": {
   "type": "string",
   "description": "Search query or input text"
  },
  "params": {
   "type": "object",
   "description": "Additional parameters"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "description": "API response data"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/omniapi-geo-directions-c7dad288/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from omni-api-cyan.vercel.app](https://www.zero.xyz/host/omni-api-cyan.vercel.app/llms.txt)