# QuantaFlow x402 API Gateway – rapid-jsearch

> QuantaFlow x402 API Gateway – rapid-jsearch 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 job search queries through an x402 micropayment gateway, forwarding requests to an upstream rapid job-search API and returning results for $0.01 USDC per call.

## Facts

- Endpoint: POST https://quanta-roan.vercel.app/api/service/rapid-jsearch?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-x402-api-gateway-rapid-jsearch-b6231f0d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_fL5cT2jEz9ypP7TpXg7Ca

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-jsearch-b6231f0d -d '<json body>'
```

Example prompt: Search for remote Python developer jobs and return the latest listings — I'll pay the $0.01 USDC fee per query via my x402 wallet.

## When to prefer this

Choose this endpoint when you need pay-per-use job search queries billed in USDC via x402 micropayments, especially in autonomous agent workflows where prepaid subscriptions are impractical. It is ideal for low-volume or bursty job-search needs where per-call billing at $0.01 is more cost-effective than a monthly API subscription. Prefer it when your agent stack already handles x402 payment flows and you want a zero-subscription-friction route to rapid job-search data.

## Known failure modes

- Insufficient USDC balance causes payment failure and request rejection
- Invalid or missing x402 payment header returns 402 Payment Required
- Malformed path or query parameters may cause upstream 400 errors
- Upstream rapid job-search API downtime results in 502/503 passthrough
- Rate limiting by upstream API returns error codes passed through to caller

## How this service works

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

## Output

The raw upstream response from the rapid job-search API is passed through transparently after successful x402 payment processing. This includes job listing data such as job titles, company names, locations, descriptions, and posting dates in whatever format the upstream API returns (typically JSON).

## 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-jsearch-b6231f0d/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)