# QuantaFlow x402 API Gateway – PostHog Proxy

> QuantaFlow x402 API Gateway – PostHog Proxy 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-21).

Proxies paid API requests to PostHog analytics via the x402 micropayment protocol, charging $0.01 USDC per call.

## Facts

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

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-x402-api-gateway-posthog-proxy-45a2952e -d '<json body>'
```

Example prompt: Forward a GET request to PostHog's /api/projects/my_project/events path with query filter ?event=page_view and charge my wallet the $0.01 USDC fee via the x402 gateway.

## When to prefer this

Choose this endpoint when you need to access PostHog analytics APIs in a permissionless, pay-per-call manner using USDC micropayments via the x402 protocol — particularly useful for autonomous AI agents that lack traditional API key management but can execute on-chain micropayments. Prefer this over direct PostHog API access when operating in a web3-native or DeFi context where crypto-native payment rails are preferable to subscription billing.

## Known failure modes

- Payment failure: insufficient USDC balance causes 402 Payment Required with no upstream call made
- Invalid path: malformed or unauthorized PostHog path returns upstream 4xx error
- Bad JSON body: malformed body string causes upstream 400 from PostHog
- Rate limiting: PostHog upstream rate limits may return 429
- Network error: upstream PostHog service unavailability causes 502 or 503

## How this service works

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

## Output

The raw response body and content type from PostHog's API, passed through transparently after successful $0.01 USDC x402 payment verification. The agent receives exactly what PostHog would return for the equivalent direct API call.

## 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-x402-api-gateway-posthog-proxy-45a2952e/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)