# Meta-API Router

> Meta-API Router is a paid API for AI agents from meta-api-router.johntaylor1online.workers.dev, paid per call via x402, $0.05/call, status unknown (last checked 2026-10-10).

Routes an incoming HTTP POST request to the most appropriate downstream API based on intelligent matching logic

## Facts

- Endpoint: POST https://meta-api-router.johntaylor1online.workers.dev/route?utm_source=zero.xyz
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-10
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/meta-api-router-9175a61a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_8VxMfvmLQ_vH3ELgstsSo

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 meta-api-router-9175a61a -d '<json body>'
```

Example prompt: Route this POST request through the meta-API router — it's a JSON body and I need it intelligently dispatched to whichever downstream API fits best.

## When to prefer this

Choose this endpoint when you need a single abstraction layer that intelligently selects among multiple possible downstream APIs without hardcoding routing logic. Useful in agentic workflows where the right API target may vary based on request content, or when building systems that need to scale across heterogeneous APIs without per-endpoint logic.

## Known failure modes

- No matching downstream API found for the input — router returns an error or empty result
- Malformed request body causing routing logic to fail
- Downstream API is unavailable or returns an error after routing
- Payment of 0.05 USDC not processed correctly, resulting in 402 rejection
- Ambiguous input causing the router to select an incorrect or suboptimal API

## How this service works

Meta-API Router — intelligent API routing

## Output

The agent receives the response from whichever downstream API the router selected, potentially including the chosen endpoint, routing metadata, and the actual API response payload as a JSON object.

## Request schema (JSON Schema)

```json
{
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input",
  "output"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "body": {},
     "enum": [
      "POST"
     ],
     "type": "string",
     "bodyType": "json"
    }
   },
   "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/meta-api-router-9175a61a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from meta-api-router.johntaylor1online.workers.dev](https://www.zero.xyz/host/meta-api-router.johntaylor1online.workers.dev/llms.txt)