# httpay.xyz API Gateway: Resend Email API

> httpay.xyz API Gateway: Resend Email API is a paid API for AI agents from httpay.xyz, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-13).

Proxies requests to the Resend email API through a pay-per-call x402 payment gateway, enabling transactional email sending and management without a direct Resend API key

## Facts

- Endpoint: POST https://httpay.xyz/api/gateway/resend/%7B*path%7D
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/httpay-xyz-api-gateway-resend-email-api-10c12a2e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_vq1MP_9PwVk6l6Aeu0DK6

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 httpay-xyz-api-gateway-resend-email-api-10c12a2e -d '<json body>'
```

Example prompt: Send a transactional email via Resend to user@example.com from noreply@mydomain.com with subject 'Your order is confirmed' and body 'Thanks for your purchase! Your order #12345 is on its way.' — route it through the httpay Resend gateway.

## When to prefer this

Choose this endpoint when you need to send transactional emails via the Resend API on a pay-per-use basis without managing your own Resend API key or subscription, especially in agent workflows using the x402 micropayment protocol where per-call billing is preferred over monthly subscriptions.

## Known failure modes

- Payment failure: insufficient USDC balance or x402 payment not accepted — results in 402 Payment Required
- Invalid Resend API path: unrecognized or malformed path segment — returns 404 or 400
- Resend API error: invalid recipient, missing required fields, or rate limiting — mirrors Resend's error response
- Authentication/authorization issue with underlying Resend service — returns 401 or 403
- Network timeout proxying to Resend — returns 504 Gateway Timeout

## How this service works

API Gateway: Resend email API

## Output

Returns the Resend API response for the requested operation, including a message ID and delivery status confirming whether the email was accepted for delivery, mirroring the standard Resend API response structure.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/httpay-xyz-api-gateway-resend-email-api-10c12a2e/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from httpay.xyz](https://www.zero.xyz/host/httpay.xyz/llms.txt)