# Proofwire Email Inbox Provisioning

> Proofwire Email Inbox Provisioning is a paid API for AI agents from verify.reversecaptcha.fun, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-20).

Issues a disposable seed email address that an agent can receive mail to, then check for delivery confirmation with SPF/DKIM/DMARC alignment

## Facts

- Endpoint: POST https://verify.reversecaptcha.fun/v1/verify/email/inbox?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/proofwire-email-inbox-provisioning-2e933497
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_SbWkG_J7OoXf5lu1c0VlE

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 proofwire-email-inbox-provisioning-2e933497 -d '<json body>'
```

Example prompt: Set up a temporary verification inbox that lasts 48 hours so I can send a test message to it and confirm my email system is delivering correctly with proper authentication.

## When to prefer this

Use this endpoint when you need cryptographically attested proof that an email address is reachable and that outbound mail passes SPF/DKIM/DMARC alignment — not just a syntax check. It is the right choice when an AI agent needs to close the loop on its own email-sending work with falsifiable, Ed25519-signed evidence. Prefer it over generic SMTP testers when you need an auditable verdict with signed headers rather than just a delivery log.

## Known failure modes

- ttl_hours exceeds maximum of 72 — request rejected with validation error
- Payment not completed via x402 — 402 response returned, inbox not created
- Service unavailable — inbox provisioning fails, no address issued
- Invalid request body — malformed JSON or unexpected field types returns 400

## How this service works

Close the loop on your own work with one paid call that returns a verdict plus Ed25519-signed, falsifiable evidence (verify signatures with GET /v1/keys). GET /v1/verify/http checks a URL is alive (redirect chain, TLS, latency, body hash). GET /v1/verify/dns resolves records and parses SPF/DMARC/DKIM. Email: POST /v1/verify/email/inbox issues a seed address; send mail to it, then GET /v1/verify/email?inbox=&token= returns delivery plus SPF/DKIM/DMARC alignment and raw headers (polls inside the paid window are free). Webhooks: POST /v1/verify/webhook arms a tripwire URL; register it upstream, then poll GET /v1/verify/webhook/{id}?token= for free. GET /v1/verify/page renders a page in a real browser, asserts a selector/text, and returns a screenshot URL. Failed work is never settled.

## Output

Returns a JSON object containing: inbox name/ID (e.g. 'check-7f3a1b2c'), a bearer token for subsequent poll calls, the full email address to send mail to (e.g. 'check-7f3a1b2c@inbox.example'), a verdict of 'issued', and an expiry timestamp. The token and inbox ID are used in free follow-up GET /v1/verify/email calls within the paid window to retrieve delivery status, SPF/DKIM/DMARC alignment, and raw headers.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "ttl_hours": {
   "type": "number",
   "maximum": 72
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "inbox": "check-7f3a1b2c",
  "token": "inb_...",
  "address": "check-7f3a1b2c@inbox.example",
  "verdict": "issued",
  "expires_at": "2026-01-01T00:00:00Z"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/proofwire-email-inbox-provisioning-2e933497/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from verify.reversecaptcha.fun](https://www.zero.xyz/host/verify.reversecaptcha.fun/llms.txt)