# ShieldAPI Email Breach Check

> ShieldAPI Email Breach 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 an email address against known data breach databases to determine if it has been compromised

## Facts

- Endpoint: GET https://shield.vainplex.dev/api/cdp/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/shield-vainplex-dev-e571c7e2
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_hcD6xUmq5O-KCM4X7iFJl

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 shield-vainplex-dev-e571c7e2
```

Example prompt: Has the email address john.doe@gmail.com ever shown up in any known data breaches or credential leaks? I want to know if it's been compromised.

## When to prefer this

Use this endpoint when you need to check a single email address against breach databases for security intelligence, identity protection workflows, or user onboarding risk assessment. Prefer this over the full security scan endpoint when you only need email breach data and want to minimize cost ($0.005 vs higher cost full scan).

## Known failure modes

- Invalid or malformed email address returns an error
- Email not found in any breach database returns empty result
- Rate limiting or payment failure (x402) if USDC balance is insufficient
- Network timeout for large breach dataset responses
- Missing required 'email' query parameter returns validation error

## How this service works

ShieldAPI - x402 security preflight before agents trust an identity, sender, or email counterparty

## Output

Returns breach intelligence data for the queried email address, including details about known data breaches the email appeared in, such as breach names, dates, and types of data exposed. The response is large (up to ~188KB) suggesting comprehensive breach database coverage.

## Example request

```json
{
 "input": {
  "type": "http",
  "method": "GET",
  "queryParams": {
   "email": "test@example.com"
  }
 }
}
```

## 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": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "email"
     ],
     "properties": {
      "email": {
       "type": "string",
       "description": "Email address to check for data breaches"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/shield-vainplex-dev-e571c7e2/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)