# Horizon Pulse PII Scanner

> Horizon Pulse PII Scanner is a paid API for AI agents from horizonpulse.dev, paid per call via x402, $0.02/call, status unknown (last checked 2026-11-20).

Scans submitted text for sensitive patterns including emails, phone numbers, SSNs, credit card numbers, IBANs, IP addresses, private keys, seed phrases, and API keys, with optional redaction.

## Facts

- Endpoint: GET https://horizonpulse.dev/api/text/pii-scan?utm_source=zero.xyz
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/horizon-pulse-pii-scanner-5021ff63
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_SNFbteWIQKZ49WALyrJOj

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 horizon-pulse-pii-scanner-5021ff63
```

Example prompt: Can you scan this text for any sensitive info like credit card numbers, SSNs, emails, API keys, or crypto seed phrases, and give me back a redacted version? Here's the text: 'Contact John at john@example.com or 555-123-4567; his SSN is 123-45-6789 and card is 4111111111111111.'

## When to prefer this

Choose this endpoint when you need fast, best-effort detection of a wide variety of sensitive data patterns (PII, financial, cryptographic) in arbitrary text, especially when you also want optional in-place redaction. It is particularly useful for pre-storage sanitization, outbound content screening, or security auditing pipelines. Prefer it over regex-only DIY approaches when you need coverage of card Luhn checks, IBAN mod-97 validation, BIP-39 seed phrase detection, and API-key shape recognition in a single call. Not suitable as a formal compliance or regulatory audit tool.

## Known failure modes

- Malformed JSON input returns an error without charge
- False negatives possible — best-effort scan may miss non-standard or obfuscated patterns
- False positives possible — Luhn/mod-97 checks reduce but don't eliminate them
- Text exceeding size limits may be rejected
- No charge for bad/invalid input
- Does not assess regulatory compliance — informational only

## How this service works

Best-effort scan of supplied text for common patterns: email, phone, US SSN, Luhn-checked card numbers, mod-97 IBANs, IP addresses, private-key shapes, BIP-39 seed phrases and API-key shapes. POST JSON {text, redact?}. Returns findings with type and offsets; redacted text only when redact is true. Best-effort only, not a compliance assessment. Informational only, no warranty. This service does not log or store the text you submit. USDC on Base or Polygon. Bad input is not charged.

## Output

A JSON response containing an array of findings, each with the detected pattern type (e.g. email, phone, SSN, credit_card, IBAN, IP, private_key, seed_phrase, api_key) and the character start/end offsets within the original text. When redact=true is passed, a redacted version of the text is also returned with sensitive values masked. The response does not include compliance assessments or guarantees.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "text": {
   "type": "string",
   "description": "Text to scan (required), up to 64 KiB."
  },
  "redact": {
   "type": "boolean",
   "description": "Optional: also return the text with findings replaced by [TYPE] labels."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/horizon-pulse-pii-scanner-5021ff63/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from horizonpulse.dev](https://www.zero.xyz/host/horizonpulse.dev/llms.txt)
