# QuantaFlow Wikipedia Proxy (x402)

> QuantaFlow Wikipedia Proxy (x402) is a paid API for AI agents from quanta-roan.vercel.app, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-13).

Fetches Wikipedia content via a pay-per-request x402 micropayment gateway, forwarding requests to the Wikipedia upstream and returning the response.

## Facts

- Endpoint: POST https://quanta-roan.vercel.app/api/service/wikipedia?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/quantaflow-wikipedia-proxy-x402-1ea270df
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_v2LNK0gYSDos9Yla4Pnje

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 quantaflow-wikipedia-proxy-x402-1ea270df -d '<json body>'
```

Example prompt: Look up the Wikipedia article for 'Quantum computing' and give me its full content — use the QuantaFlow Wikipedia proxy and forward the GET request to the /wiki/Quantum_computing path.

## When to prefer this

Choose this endpoint when you need programmatic access to Wikipedia content and are operating in a web3 or x402-enabled payment environment where micropayment-per-call billing is acceptable or preferred over API key management. It is well-suited for AI agent pipelines that already handle x402 payments and need encyclopedia lookups without setting up a separate Wikipedia integration.

## Known failure modes

- Payment failure: x402 payment not authorized or insufficient USDC balance results in 402 response
- Invalid path: malformed or non-existent Wikipedia article path returns upstream 404
- Rate limiting: upstream Wikipedia rate limits may propagate through the proxy
- Upstream unavailability: Wikipedia downtime causes proxy to return an error
- Schema mismatch: improperly formatted query object or body may cause request forwarding failure

## How this service works

Every request, a quantum of value. x402 protocol-based payment endpoint for web3/DeFi tools.

## Output

The raw upstream Wikipedia response body (HTML, JSON, or plain text depending on the path and query) along with its content type, passed through transparently after the x402 micropayment is settled.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "body": {
   "type": "string",
   "description": "Optional JSON body forwarded to POST requests."
  },
  "path": {
   "type": "string",
   "description": "Path below the selected upstream origin."
  },
  "query": {
   "type": "object"
  },
  "method": {
   "enum": [
    "GET",
    "POST"
   ],
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "description": "The upstream response body and content type are passed through after successful payment."
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/quantaflow-wikipedia-proxy-x402-1ea270df/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from quanta-roan.vercel.app](https://www.zero.xyz/host/quanta-roan.vercel.app/llms.txt)