# DDG Password Breach Check

> DDG Password Breach Check is a paid API for AI agents from agents.daedalusdevelopmentgroup.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-22).

Checks whether a given password appears in known data breach corpora using the HIBP Pwned Passwords k-anonymity range API, without exposing the full password.

## Facts

- Endpoint: POST https://agents.daedalusdevelopmentgroup.com/v1/password-breach-check?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-22
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/ddg-password-breach-check-8785f76b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_PldFcawUcbM1CMKxglj7P

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 ddg-password-breach-check-8785f76b -d '<json body>'
```

Example prompt: Can you check whether the password 'Tr0ub4dor&3' has ever appeared in a known data breach, using a privacy-preserving k-anonymity check so the actual password is never sent over the wire?

## When to prefer this

Choose this endpoint when you need a privacy-preserving breach check that never exposes the full password — it uses k-anonymity so only a 5-char SHA-1 prefix is transmitted. Prefer this over rolling your own HIBP integration when you want a simple, agent-payable API call without managing API keys or HIBP rate limits directly. Ideal for AI agents that need to enforce password hygiene at account creation or credential rotation workflows.

## Known failure modes

- Invalid or malformed SHA-1 hash input returns an error
- Missing required body fields returns a validation error
- HIBP upstream service unavailability causes request failure
- Payment of 0.01 USDC not provided or rejected causes 402 response
- Rate limiting if too many requests are made in quick succession

## How this service works

Checks whether a password appears in known breach corpora via the HIBP Pwned Passwords range API with k-anonymity: only a 5-char SHA-1 prefix leaves the edge, and the password is never stored, logged or echoed. Accepts a raw password or a caller-computed SHA-1.

## Output

Returns a boolean indicating whether the password was found in known breach corpora, along with how many times it appeared across breached datasets. The full password never leaves the caller — only a 5-character SHA-1 prefix is transmitted to preserve k-anonymity.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input",
  "output"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {
     "type": "object"
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST",
      "PUT",
      "PATCH"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json",
      "form-data",
      "text"
     ],
     "type": "string"
    }
   },
   "additionalProperties": true
  },
  "output": {
   "type": "object",
   "required": [
    "type",
    "example"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "ok": true
    }
   },
   "additionalProperties": true
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/ddg-password-breach-check-8785f76b/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agents.daedalusdevelopmentgroup.com](https://www.zero.xyz/host/agents.daedalusdevelopmentgroup.com/llms.txt)