# Saylor Innovations Password Breach Check by SHA-1

> Saylor Innovations Password Breach Check by SHA-1 is a paid API for AI agents from saylorinnovations.com, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-01).

Checks whether a password appears in known data breaches using its SHA-1 hash prefix via the Have I Been Pwned k-anonymity range API, returning breach status and exposure count.

## Facts

- Endpoint: GET https://saylorinnovations.com/api/breach/password?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-01
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/saylor-innovations-password-breach-check-by-sha-1-43d89dae
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_dX7neQnzG5q4MIL1PAM_g

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 saylor-innovations-password-breach-check-by-sha-1-43d89dae
```

Example prompt: Can you check if the password 'Summer2024!' has ever shown up in a data breach — hash it to SHA-1 first and use the breach check API so the actual password is never sent?

## When to prefer this

Use this endpoint when you need a privacy-preserving breach check that never exposes the raw password — it uses the k-anonymity model so only a hash prefix is sent to the upstream HIBP service. Prefer this over full-password submission approaches or manual HIBP API integration when you need a simple, pay-per-call microservice with no API key management.

## Known failure modes

- Invalid or malformed SHA-1 hash (not 40 hex characters) returns an error
- Network timeout or upstream HIBP service unavailability
- Missing 'sha1' query parameter causes bad request response
- Hash provided is not lowercase/uppercase normalized as expected

## How this service works

Password Breach Check by SHA-1 (Have I Been Pwned) — Security

## Output

Returns a JSON object with a 'pwned' boolean indicating whether the password hash has appeared in known breach datasets, and a 'times_seen' number showing how many times it has been observed across all breaches. No raw password data is ever transmitted.

## 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",
      "POST",
      "PUT",
      "PATCH",
      "DELETE",
      "HEAD"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {
      "sha1": {
       "type": "string",
       "description": "40-hex SHA-1 hash of the password; never send the password itself (query)"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "json"
    },
    "example": {
     "type": "object",
     "required": [
      "pwned"
     ],
     "properties": {
      "pwned": {
       "type": "boolean"
      },
      "times_seen": {
       "type": "number"
      }
     }
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/saylor-innovations-password-breach-check-by-sha-1-43d89dae/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from saylorinnovations.com](https://www.zero.xyz/host/saylorinnovations.com/llms.txt)