# QuantaFlow Polymarket Bridge

> QuantaFlow Polymarket Bridge 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-14).

Proxies requests to the Polymarket prediction market API via x402 micropayment-gated gateway, passing through responses after successful USDC payment.

## Facts

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

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-polymarket-bridge-e7bebe9c -d '<json body>'
```

Example prompt: Can you pull the current odds for the 2024 US presidential election market on Polymarket — I need the latest prices and volume for each outcome.

## When to prefer this

Use this endpoint when you need programmatic access to Polymarket prediction market data and are operating in a web3/x402 micropayment context. Prefer this over direct Polymarket API access when your agent infrastructure is already set up for x402 payments and you want per-call billing at $0.01 USDC rather than managing API keys or subscriptions.

## Known failure modes

- Payment failure: insufficient USDC balance or wallet not configured for x402 micropayments
- Invalid path: the specified Polymarket API path does not exist, returning a 404 from upstream
- Malformed query or body: Polymarket rejects the forwarded request due to invalid parameters
- Polymarket API downtime: upstream service unavailable, returning a 502 or 503
- Rate limiting: Polymarket upstream rate-limits the gateway IP, causing 429 errors

## How this service works

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

## Output

The raw upstream Polymarket API response body is passed through after payment is processed, including market data, prices, order books, or any other Polymarket endpoint response, along with the content type header.

## 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-polymarket-bridge-e7bebe9c/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)