# OmniAPI Geo Routing

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

Determines optimal network or geographic routing paths based on a query, returning routing recommendations or geolocation-based route data.

## Facts

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

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-routing-ef1e9f5e -d '<json body>'
```

Example prompt: Can you figure out the best geographic routing path for traffic coming from 'New York to London' using the OmniAPI geo routing endpoint?

## When to prefer this

Use this endpoint when you need a quick, pay-per-call geo routing decision without managing your own routing infrastructure. It is particularly useful in agentic workflows that need to dynamically determine geographic routing for traffic, users, or services, and want to pay fractionally in USDC rather than subscribing to a routing service.

## Known failure modes

- Missing required 'query' field returns a validation error
- Ambiguous or malformed query string may return a generic or unhelpful routing result
- Service may return an opaque API response object if the backend routing logic fails
- Payment failure via x402 (insufficient USDC balance) blocks the call entirely
- Vercel cold-start latency may cause occasional slow responses

## 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

Returns a routing recommendation or geographic routing decision, likely including the suggested route, region, or destination endpoint based on the query input. The exact schema is generic but expected to contain routing path or location-based direction data.

## 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-routing-ef1e9f5e/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)