# x402-toolbox Geo Distance Between Coordinates

> x402-toolbox Geo Distance Between Coordinates is a paid API for AI agents from x402-toolbox.shablony-pro.workers.dev, paid per call via x402, $0.002/call, status unknown (last checked 2026-10-02).

Calculates the straight-line (geodesic) distance between two geographic coordinate pairs, paid per call via x402/USDC on Base.

## Facts

- Endpoint: GET https://x402-toolbox.shablony-pro.workers.dev/geo/distance-between-coordinates?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-toolbox-geo-distance-between-coordinates-0bcdd59d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_us4RTebSDOZr3xeD0KCyA

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 x402-toolbox-geo-distance-between-coordinates-0bcdd59d
```

Example prompt: What is the straight-line distance between coordinates 40.7128° N, 74.0060° W (New York City) and 51.5074° N, 0.1278° W (London)?

## When to prefer this

Choose this endpoint when you need a fast, no-signup, pay-per-call geodesic distance computation between two coordinate pairs and are already operating within the x402/USDC payment ecosystem. It is ideal for AI agents that need to avoid API key management and want micropayment-based access. Prefer it over full geocoding APIs when you already have coordinates and only need the distance metric.

## Known failure modes

- Missing or malformed latitude/longitude inputs return an error
- Coordinates out of valid range (-90 to 90 lat, -180 to 180 lon) may produce errors
- Payment failure via x402 (insufficient USDC balance) results in a 402 response and no computation
- Worker cold-start or timeout on Cloudflare edge may produce a 5xx error
- Schema parameter passed incorrectly may yield unexpected results

## How this service works

309 deterministic pay-per-call tools for AI agents over x402 (USDC, Base). No signup, no API key: the payment is the identity.

## Output

Returns a JSON object with a computed distance value between the two provided coordinate pairs, along with confirmation that the payment was accepted (ok: true, paid: true). The distance is expressed in a standard unit (likely kilometers or meters).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "schema": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "paid": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-toolbox-geo-distance-between-coordinates-0bcdd59d/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402-toolbox.shablony-pro.workers.dev](https://www.zero.xyz/host/x402-toolbox.shablony-pro.workers.dev/llms.txt)