# Prysm Resend Email Provider

> Prysm Resend Email Provider is a paid API for AI agents from prysm-kappa.vercel.app, paid per call via x402, $0.1/call, status unknown (last checked 2026-09-14).

Sends transactional emails via Resend through the Prysm x402 pay-per-call gateway on Base mainnet

## Facts

- Endpoint: POST https://prysm-kappa.vercel.app/api/v1/providers/resend
- Price: $0.1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/prysm-resend-email-provider-9c5e6aca
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_H8wlIGNwToM5GVBYjHNlC

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 prysm-resend-email-provider-9c5e6aca -d '<json body>'
```

Example prompt: Send a transactional email using the Resend provider — use the 'send' operation and deliver it to jane@example.com from noreply@myapp.com with the subject 'Your order has shipped' and a plain-text body saying 'Your order #1234 is on its way!'

## When to prefer this

Choose this endpoint when your AI agent needs to send transactional emails programmatically and you want a pay-per-call model billed in USDC on Base mainnet via x402 — ideal for agent workflows that need email delivery without managing long-term API subscriptions or Resend credentials directly. Prefer this over direct Resend API calls when operating in a crypto-native or x402-compatible agent environment.

## Known failure modes

- Invalid or missing recipient email address returns a validation error
- Insufficient USDC balance or x402 payment failure prevents the call from executing
- Unauthorized sender domain (not verified in Resend) causes delivery rejection
- Malformed input object or missing required fields returns a 400-level error
- Rate limiting or Resend API downtime results in a 5xx error response

## How this service works

Prysm sells paid, agent-ready provider capabilities over x402 on Base mainnet using USDC.

## Output

Returns a JSON object containing a 'data' field with the Resend API response (including message ID and delivery status), the 'provider' field set to 'resend', and the 'operation' field set to 'send'.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "input": {
   "type": "object",
   "description": "Provider-specific operation parameters.",
   "additionalProperties": true
  },
  "operation": {
   "type": "string",
   "description": "Allowlisted operation for the selected provider."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": {},
  "provider": "resend",
  "operation": "send"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/prysm-resend-email-provider-9c5e6aca/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from prysm-kappa.vercel.app](https://www.zero.xyz/host/prysm-kappa.vercel.app/llms.txt)