# Proofwire Email Delivery Verification

> Proofwire Email Delivery Verification is a paid API for AI agents from verify.reversecaptcha.fun, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-21).

Polls a Proofwire seed inbox to confirm email delivery and returns SPF/DKIM/DMARC authentication alignment results with Ed25519-signed evidence

## Facts

- Endpoint: GET https://verify.reversecaptcha.fun/v1/verify/email?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-21
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/proofwire-email-delivery-verification-8ad47b1e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_5Fa53zrMs5Ho54ZtdIANF

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-delivery-verification-8ad47b1e
```

Example prompt: Check whether the email I just sent from noreply@acme.com was delivered to the Proofwire seed inbox — use inbox ID 'inbox_abc123' and token 'tok_xyz789' — and tell me if SPF, DKIM, and DMARC all passed.

## When to prefer this

Choose this endpoint when you need cryptographically signed proof that an email was actually delivered and authenticated — not just that an SMTP server accepted it. It is the right choice when you want SPF/DKIM/DMARC alignment details bundled with falsifiable evidence, especially in agentic pipelines where 'closing the loop' on sent email matters. Prefer it over SMTP delivery logs or open-tracking pixels when tamper-proof audit trails are required.

## Known failure modes

- Email not yet delivered within polling window — verdict may be pending or undelivered
- Invalid or expired token returns 401/403
- Inbox ID not found returns 404
- SPF/DKIM/DMARC failures reflected in verdict but not an API error — verdict will indicate failure rather than delivery
- Payment not settled (x402) — call blocked before execution
- Rate limiting or window expiry if polled outside the paid window

## 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 verdict field ('delivered' or failure), the raw email headers including Received lines, per-mechanism authentication results (SPF pass/fail, DKIM result and alignment flag, DMARC result), the timestamp of delivery, and the entire evidence bundle signed with an Ed25519 key verifiable via GET /v1/keys.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "const": "http"
    },
    "method": {
     "const": "GET"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "inbox",
      "token"
     ],
     "properties": {
      "from": {
       "type": "string"
      },
      "wait": {
       "type": "string"
      },
      "inbox": {
       "type": "string"
      },
      "token": {
       "type": "string"
      },
      "window": {
       "type": "string"
      },
      "match_subject": {
       "type": "string"
      }
     }
    }
   }
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "verdict": "delivered",
  "evidence": {
   "message": {
    "raw_headers": "Received: ...",
    "received_at": "2026-01-01T00:00:00Z",
    "authentication": {
     "spf": {
      "result": "pass"
     },
     "dkim": [
      {
       "result": "pass",
       "aligned": true
      }
     ],
     "dmarc": {
      "result": "pass"
     }
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/proofwire-email-delivery-verification-8ad47b1e/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)