# Verdict PII Scanner

> Verdict PII Scanner is a paid API for AI agents from verdict.kechlab.com, paid per call via x402, $0.0337/call, status unknown (last checked 2026-10-21).

Scans text for personally identifiable information (PII) using AI-level detection beyond regex, identifying names, addresses, IDs, health data, credentials, emails, IBANs, payment cards, and phone numbers — without rewriting the text.

## Facts

- Endpoint: POST https://verdict.kechlab.com/v1/pii-scan?utm_source=zero.xyz
- Price: $0.0337/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-21
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/verdict-pii-scanner-73c54ca0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_CDDTOGojvMzl4mJgygtsM

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 verdict-pii-scanner-73c54ca0 -d '<json body>'
```

Example prompt: Scan this support ticket text for any PII — especially names, email addresses, phone numbers, payment cards, and IBANs — and tell me exactly what you find: 'Hi, I'm John Smith, my card ending 4532 was charged twice, please contact me at john.smith@gmail.com or +1-555-234-9871.'

## When to prefer this

Choose this endpoint when regex-based PII detection is insufficient — e.g. when you need to catch natural-language names and postal addresses that don't match fixed patterns, or when you need format validation (Luhn-checked card numbers, valid IBANs) alongside semantic detection. Ideal for compliance pipelines, data ingestion guardrails, and outbound content checks where both recall (finding what regex misses) and precision (validating structured identifiers) matter. Not suitable if you need the text rewritten or redacted — this endpoint only detects and locates.

## Known failure modes

- Empty or whitespace-only text input returns no detections
- Very long text may require chunking if it exceeds token limits
- Highly ambiguous names in generic contexts may produce false positives
- Unusual or non-standard ID number formats from obscure jurisdictions may be missed
- Specifying an invalid PII type in the `types` filter may result in an error or ignored filter
- Adversarially obfuscated PII (e.g. leetspeak substitutions) may evade detection

## How this service works

PII detector that finds what regex misses (names, addresses, ID numbers, health data, credentials) and locates what patterns can verify (emails, valid IBANs, Luhn-checked cards, phones). Does not rewrite text.

## Output

Returns a structured list of detected PII entities found in the input text, including the PII category (e.g. person_name, email, payment_card, bank_account), the matched value or span, and — where applicable — validation results such as Luhn check for cards or IBAN format validity. Does not return rewritten or redacted text.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "text": {
   "type": "string",
   "description": "the text to examine"
  },
  "types": {
   "description": "(optional) subset of: person_name, email, phone, postal_address, id_number, payment_card, bank_account, date_of_birth, credentials, health_info"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/verdict-pii-scanner-73c54ca0/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from verdict.kechlab.com](https://www.zero.xyz/host/verdict.kechlab.com/llms.txt)