# QuantaFlow x402 API Gateway – Resend Proxy

> QuantaFlow x402 API Gateway – Resend 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-13).

Forwards HTTP requests to the Resend email API via an x402 micropayment-gated proxy, charging $0.01 USDC per call.

## Facts

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

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-resend-proxy-d3a6c44a -d '<json body>'
```

Example prompt: Send a transactional email via the QuantaFlow x402 gateway to user@example.com with subject 'Your order is confirmed' and body 'Thanks for your purchase!' — route it through the Resend path with a POST to /emails.

## When to prefer this

Choose this endpoint when you need to send transactional email via Resend but want pay-per-use micropayment billing in USDC rather than a traditional monthly subscription, or when operating in a web3/DeFi context where x402 protocol payments are already part of your agent's payment stack.

## Known failure modes

- Insufficient USDC balance causes x402 payment failure and request is rejected before forwarding
- Invalid or malformed JSON body results in upstream Resend API error passed through
- Incorrect path causes 404 or routing error from Resend
- Missing required Resend fields (e.g. to/from/subject) result in 4xx from upstream
- Network or upstream Resend outage returns 502/503 passthrough error
- Malformed query object causes request construction failure

## How this service works

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

## Output

Returns the upstream Resend API response body (e.g. message ID, delivery status) and content type, passed through transparently after the x402 micropayment is validated.

## 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-resend-proxy-d3a6c44a/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)