# X402 Hub – Apiton Query Endpoint

> X402 Hub – Apiton Query Endpoint is a paid API for AI agents from x402-hub.vercel.app, paid per call via x402, $0.068723/call, status unknown (last checked 2026-10-20).

Sends a query string to a micropayment-gated API aggregator and returns structured data from one of 63 upstream paid endpoints, billed per call via x402 on Base.

## Facts

- Endpoint: POST https://x402-hub.vercel.app/api/apiton?utm_source=zero.xyz
- Price: $0.068723/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-hub-apiton-query-endpoint-3f0f7ffa
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_gBlNxa-TuHLgfk1N6mF5_

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-apiton-query-endpoint-3f0f7ffa -d '<json body>'
```

Example prompt: Search the X402 Hub apiton endpoint with the query 'latest ETH price' and return the structured data response — it charges about $0.07 per call via x402 on Base.

## When to prefer this

Choose this endpoint when you want per-call access to any of 63 paid APIs without managing individual API keys or subscriptions, and you are comfortable paying ~$0.07 USDC per call via x402 micropayments on Base. It is ideal for agentic workflows that need occasional, pay-as-you-go data lookups across multiple domains through a single interface. Prefer alternatives if you need guaranteed schema stability, heavy-volume discounts, or know exactly which upstream provider you need and can integrate directly.

## Known failure modes

- Payment failure: insufficient USDC balance on Base causes a 402 response and no data is returned
- Ambiguous query: the query string doesn't map clearly to an upstream endpoint, resulting in an error or empty data
- Upstream API unavailability: one of the 63 upstream services is down, returning an error inside the data object
- Malformed request: missing required 'query' field causes a 400 validation error
- Rate limiting: excessive calls in a short window may trigger throttling from upstream providers

## How this service works

63 paid API endpoints protected by x402 micropayments on Base

## Output

Returns a JSON object with a top-level 'data' field containing the structured response from whichever upstream API handled the query. The shape of data varies depending on which of the 63 upstream endpoints the hub routes the query to.

## 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-apiton-query-endpoint-3f0f7ffa/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)