# QuantaFlow x402 API Gateway – rapid-onecash

> QuantaFlow x402 API Gateway – rapid-onecash 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-12).

Proxies requests to the rapid-onecash upstream service via the x402 micropayment protocol, charging $0.01 USDC per call.

## Facts

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

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-rapid-onecash-b183f102 -d '<json body>'
```

Example prompt: Forward a POST request to the rapid-onecash service at path '/convert' with body '{"amount":100,"currency":"USD"}' through QuantaFlow, paying the $0.01 USDC x402 fee automatically.

## When to prefer this

Choose this endpoint when you specifically need to access the rapid-onecash upstream service and want to pay per-call using the x402 USDC micropayment protocol without setting up your own billing or API key arrangement. Prefer this over direct API calls when you want a Coinbase-ecosystem-compatible pay-as-you-go model for DeFi/web3 tooling.

## Known failure modes

- Payment failure: insufficient USDC balance causes x402 payment to fail and request is not forwarded
- Upstream error: rapid-onecash service returns 4xx/5xx which is passed through as-is
- Invalid path: requesting a path not supported by rapid-onecash upstream returns an error
- Malformed body: invalid JSON in body field may cause upstream rejection
- Gateway timeout: rapid-onecash upstream may be slow or unavailable

## 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 the rapid-onecash upstream service, passed through transparently after the x402 micropayment of $0.01 USDC is settled. No transformation is applied to the upstream response.

## 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-rapid-onecash-b183f102/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)