# Agent Rest Stop – Route One Hop Lookup

> Agent Rest Stop – Route One Hop Lookup is a paid API for AI agents from agent-gas-station.agent-gas-station.workers.dev, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-31).

Returns a single venue (hop) from a pre-defined route table given a starting and ending asset or location.

## Facts

- Endpoint: POST https://agent-gas-station.agent-gas-station.workers.dev/v1/RouteOneHop?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-31
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agent-rest-stop-route-one-hop-lookup-62f8d92f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_CEPtuVq_Kip2Sc9VVD-zk

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 agent-rest-stop-route-one-hop-lookup-62f8d92f -d '<json body>'
```

Example prompt: Look up the venue I should use to route from USDC to ETH — I have USDC and I want ETH.

## When to prefer this

Use this endpoint when an agent needs to resolve exactly one hop from a routing table between a known starting asset and a desired target asset, particularly in multi-step automated workflows where each step must be resolved individually. Prefer it over a full route-planning service when you already know the specific pair and only need the canonical venue for that single transition.

## Known failure modes

- No route found for the given have/want pair — returns empty or null venue
- Invalid or unsupported asset/location strings — may return a 400-level error
- Route table not populated or stale — may return outdated or missing entries
- Payment of $0.01 USDC not fulfilled — 402 payment required error blocks the response

## How this service works

One venue from the route table.

## Output

A single venue record from the route table representing the recommended hop between the specified 'have' and 'want' assets or endpoints, including the venue identifier and associated routing metadata.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "have": {
   "type": "string"
  },
  "want": {
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agent-rest-stop-route-one-hop-lookup-62f8d92f/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agent-gas-station.agent-gas-station.workers.dev](https://www.zero.xyz/host/agent-gas-station.agent-gas-station.workers.dev/llms.txt)