# RelayShield Email Breach Check

> RelayShield Email Breach Check is a paid API for AI agents from api.relayshield.net, paid per call via x402, $0.1/call, status unknown (last checked 2026-09-15).

Checks whether a given email address has appeared in known data breaches, returning breach names, domains, dates, and exposed data classes

## Facts

- Endpoint: POST https://api.relayshield.net/v1/payg/breach
- Price: $0.1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/relayshield-email-breach-check-9421714f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_qUv-uPtEfDPY0sdzg_jRz

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 relayshield-email-breach-check-9421714f -d '<json body>'
```

Example prompt: Can you check if the email address john.doe@example.com has shown up in any data breaches and tell me which ones, what data was exposed, and how many total breaches it appears in?

## When to prefer this

Choose this endpoint when you need a pay-per-use, programmatic lookup of email breach history with structured output including breach names, dates, domains, and data class details. It is ideal for one-off checks, agent-driven security workflows, or building lightweight security screening into onboarding flows without requiring a subscription to a larger identity monitoring service.

## Known failure modes

- Invalid or malformed email address returns an error response
- Email not found in any breach database returns an empty breaches array with breach_count of 0
- Network timeout or upstream breach database unavailability causes a 5xx error
- Rate limiting may occur if the endpoint is called too frequently
- Payment failure via x402 protocol prevents the request from being processed

## How this service works

RelayShield Landing Site

## Output

A JSON object containing the queried email address, an array of breach records (each with breach name, domain, breach date, verification status, and list of exposed data classes such as passwords or email addresses), and a total breach count integer indicating how many breaches the email appears in.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "email": {
   "type": "string",
   "description": "Email address to check"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "data": {
   "email": "user@example.com",
   "breaches": [
    {
     "name": "ExampleBreach",
     "domain": "example.com",
     "breach_date": "2023-06-01",
     "is_verified": true,
     "data_classes": [
      "Passwords",
      "Email addresses"
     ]
    }
   ],
   "breach_count": 3
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/relayshield-email-breach-check-9421714f/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.relayshield.net](https://www.zero.xyz/host/api.relayshield.net/llms.txt)