# QuantaFlow x402 Abstract Phone API Gateway

> QuantaFlow x402 Abstract Phone API Gateway 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-10).

Proxies requests to an abstract phone upstream service via the x402 micropayment protocol, charging $0.01 USDC per call.

## Facts

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

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-abstract-phone-api-gateway-660e78df -d '<json body>'
```

Example prompt: Look up details for phone number +14155552671 using the Abstract Phone service — I'm okay paying the per-request fee automatically.

## When to prefer this

Choose this endpoint when you need pay-per-call access to the Abstract Phone service without a subscription, want automatic micropayment billing via x402/USDC, or are building a web3-native agent workflow that needs phone data with on-chain payment settlement at $0.01 per request.

## Known failure modes

- Insufficient USDC balance causes payment failure and request rejection
- Invalid or unsupported path returns upstream 404 or error
- Malformed query parameters forwarded as-is may cause upstream errors
- x402 facilitator downtime prevents payment settlement
- Upstream Abstract Phone service unavailability results in gateway timeout

## How this service works

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

## Output

The raw upstream response body and content-type from the Abstract Phone service, passed through transparently after the x402 payment is settled. Typically phone metadata such as carrier info, line type, or number validity depending on the path queried.

## 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-abstract-phone-api-gateway-660e78df/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)