# ShieldAPI Email Breach Exposure Check

> ShieldAPI Email Breach Exposure Check is a paid API for AI agents from shield.vainplex.dev, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-15).

Checks whether a given email address has been exposed in known data breaches

## Facts

- Endpoint: GET https://shield.vainplex.dev/api/check-email
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/shieldapi-email-breach-exposure-check-61f8ecda
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_NS00jtpk34GcJCk1XTDhL

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 shieldapi-email-breach-exposure-check-61f8ecda
```

Example prompt: Can you check if john.doe@example.com has ever shown up in a data breach or been exposed in any known hacks?

## When to prefer this

Use this endpoint when you need to quickly assess whether a specific email address has been exposed in known data breaches — particularly useful for security preflights before trusting an email sender, onboarding a user, or validating counterparty identity in agent workflows. Prefer this over generic HIBP-compatible lookups when you want a pay-per-call, x402-native integration with no API key management.

## Known failure modes

- Invalid email format returns validation error
- Missing email parameter returns 400 bad request
- Rate limiting or payment failure returns 402 or 429
- Email not found in any breach returns clean/safe result
- Demo mode may return synthetic or limited data

## How this service works

Email breach exposure check

## Output

Returns breach exposure status for the given email address, including whether the email was found in known breach datasets and details about the compromised data sources

## Example request

```json
{
 "demo": true,
 "prefix": "5baa6"
}
```

## Request schema (JSON Schema)

```json
{
 "properties": {
  "input": {
   "required": [
    "method"
   ],
   "properties": {
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/shieldapi-email-breach-exposure-check-61f8ecda/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from shield.vainplex.dev](https://www.zero.xyz/host/shield.vainplex.dev/llms.txt)