# X402 Hub Copilot

> X402 Hub Copilot is a paid API for AI agents from x402-hub.vercel.app, paid per call via x402, $0.125/call, status unknown (last checked 2026-10-11).

Routes a natural language query to one of 63 paid API endpoints protected by x402 micropayments on Base, returning structured data from the matched upstream service

## Facts

- Endpoint: POST https://x402-hub.vercel.app/api/copilot?utm_source=zero.xyz
- Price: $0.125/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-hub-copilot-10b1ded8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_vCxVnKaZ72YcowTDKA43V

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-hub-copilot-10b1ded8 -d '<json body>'
```

Example prompt: Use the X402 Hub copilot to look up current Bitcoin price data — just send the query 'What is the current price of Bitcoin in USD?' and let the hub route it to the right paid endpoint.

## When to prefer this

Choose this endpoint when you need to query one of a broad set of curated paid data APIs using natural language without knowing which specific API to call — it acts as a smart router and proxy. Prefer it over calling individual APIs directly when you want to avoid managing multiple API keys, x402 payment headers per-service, or endpoint discovery. Best suited for exploratory queries where the exact upstream data source is less important than getting a relevant answer quickly.

## Known failure modes

- Query too ambiguous to route to a specific upstream endpoint — returns empty or error response
- Upstream API temporarily unavailable — hub may return a 502 or partial response
- Insufficient USDC balance to cover $0.125 micropayment — x402 payment fails and request is rejected
- Query falls outside scope of all 63 available endpoints — no matching upstream found
- Malformed query string causes routing failure — returns 400 bad request
- Rate limits on upstream APIs exceeded — hub returns throttling error

## How this service works

63 paid API endpoints protected by x402 micropayments on Base

## Output

A JSON object with a 'data' field containing the structured response from whichever of the 63 upstream paid APIs the hub determined best matched the input query. The exact shape of 'data' varies by upstream service.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "query"
 ],
 "properties": {
  "query": {
   "type": "string",
   "description": "Query parameter for the API"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "data": {
   "type": "object",
   "description": "Response data from upstream API"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-hub-copilot-10b1ded8/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402-hub.vercel.app](https://www.zero.xyz/host/x402-hub.vercel.app/llms.txt)