# Password Breach Check via HIBP k-Anonymity

> Password Breach Check via HIBP k-Anonymity is a paid API for AI agents from api.x402node.dev, paid per call via x402, $0.008/call, status unknown (last checked 2026-09-14).

Checks whether a password has appeared in known data breaches using the Have I Been Pwned API with k-anonymity SHA-1 hash prefix lookup, without exposing the full password.

## Facts

- Endpoint: GET https://api.x402node.dev/password/breach
- Price: $0.008/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/api-x402node-dev-2c88ed43
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Nn8tM-57QrV8NZS0Qm0An

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 api-x402node-dev-2c88ed43
```

Example prompt: Can you check if the password 'BlueSky#2023!' has ever appeared in a known data breach — use the k-anonymity HIBP lookup so the actual password never leaves my machine?

## When to prefer this

Use this endpoint when you need a privacy-safe, k-anonymity-compliant breach check for a single password without exposing the full credential to any external server. Prefer over rolling your own HIBP integration when you need a managed, pay-per-call solution that handles the SHA-1 prefix/suffix logic automatically.

## Known failure modes

- Invalid or empty password input returns a 400 error
- HIBP upstream API unavailability causes a 502 or timeout
- Malformed request body causes a 422 validation error
- Rate limiting or payment failure returns a 402 or 429 error

## How this service works

Password breach check via Have I Been Pwned, HIBP API, k-anonymity, SHA-1 hash prefix lookup, known compromised passwords. Privacy-safe: only hash prefix sent. Accepts payment on Base or Solana — either network works.

## Output

Returns whether the password has appeared in known breach databases and how many times it was found, derived from matching SHA-1 hash suffixes returned by the HIBP range API — without transmitting the full password or hash.

## Example request

```json
{
 "password": "TestPassword123!"
}
```

## 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",
     "properties": {
      "password": {
       "type": "string",
       "description": "Password (optional)"
      }
     }
    }
   },
   "additionalProperties": false
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/api-x402node-dev-2c88ed43/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.x402node.dev](https://www.zero.xyz/host/api.x402node.dev/llms.txt)