# StatePulse Transit Route Duration

> StatePulse Transit Route Duration is a paid API for AI agents from statepulse-api.hahavoid0.workers.dev, paid per call via x402, $0.02/call, status unknown (last checked 2026-09-13).

Calculates the estimated travel distance and duration for a transit route between two points

## Facts

- Endpoint: POST https://statepulse-api.hahavoid0.workers.dev/transit/route-duration
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/statepulse-transit-route-duration-9705f44d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Q1fKtt1Pq1XZQRXr56YES

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 statepulse-transit-route-duration-9705f44d -d '<json body>'
```

Example prompt: How long will it take to travel from downtown Chicago to O'Hare Airport by transit, and what's the distance in kilometers?

## When to prefer this

Use this endpoint when you need a quick, pay-per-call transit route duration and distance estimate without managing API keys. Prefer it for AI agent workflows that need lightweight transit lookup at $0.02 per call, especially when integrating with x402/USDC micropayment flows on Base.

## Known failure modes

- Unsupported route or region returns supported:false
- Invalid or unparseable origin/destination inputs return 4xx error
- Low-confidence estimates may return confidence:'low' with approximate values
- Service unavailability from underlying transit data source returns 5xx error

## How this service works

Computes the shortest driving distance and duration between two coordinates using the public OSRM engine.

## Output

Returns a JSON object with distance_km (numeric kilometers between origin and destination), duration_minutes (estimated travel time in minutes), a supported boolean indicating whether the route is calculable, and a confidence level string (e.g. 'high').

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "result": {
   "distance_km": 18.5,
   "duration_minutes": 22.4
  },
  "supported": true,
  "confidence": "high"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/statepulse-transit-route-duration-9705f44d/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from statepulse-api.hahavoid0.workers.dev](https://www.zero.xyz/host/statepulse-api.hahavoid0.workers.dev/llms.txt)
