# x402 API Route Planner

> x402 API Route Planner is a paid API for AI agents from x402-api-production-bd43.up.railway.app, paid per call via x402, $0.02/call, status unknown (last checked 2026-10-29).

Plans a multi-step agent workflow by routing an HTTP GET request through the x402 paid API infrastructure

## Facts

- Endpoint: GET https://x402-api-production-bd43.up.railway.app/route?utm_source=zero.xyz
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-29
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-api-route-planner-a4d2a347
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_FBjFreo1z9oecDVX96SOI

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-api-route-planner-a4d2a347
```

Example prompt: Can you plan out the multi-step workflow my agent needs to follow to complete this task, routing it through the right sequence of API calls?

## When to prefer this

Choose this endpoint when you need to decompose a complex agentic task into ordered steps across multiple x402 API endpoints, particularly when working within the x402 paid API ecosystem. Prefer it over manual orchestration when the task involves sequencing calls to data APIs like prices, weather, FX, or news available on the same platform.

## Known failure modes

- Missing required 'input' object returns a validation error
- Unsupported HTTP method (non-GET) returns an enum mismatch error
- Malformed request body results in a 400 bad request
- Payment not provided or insufficient USDC balance triggers a 402 Payment Required response
- Downstream routing logic unavailable may return a 503 or empty plan

## How this service works

Plan multi-step agent workflow

## Output

Returns a planned multi-step workflow or route describing the sequence of agent actions and API calls needed to accomplish a given task, likely including step identifiers, endpoint references, and ordering logic.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {}
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-api-route-planner-a4d2a347/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402-api-production-bd43.up.railway.app](https://www.zero.xyz/host/x402-api-production-bd43.up.railway.app/llms.txt)