# Verity Suite – Quick Redact

> Verity Suite – Quick Redact is a paid API for AI agents from suite.veritylayer.dev, paid per call via x402, $0.02/call, status unknown (last checked 2026-09-14).

Scans a text payload for PII, secrets, and credentials, returning a verdict, severity, findings, and reasons — with an optional Ed25519-signed receipt.

## Facts

- Endpoint: POST https://suite.veritylayer.dev/redact/quick
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/verity-suite-quick-redact-6fff95e3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_t3Ey5nANE_jBvwINmTRzY

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 verity-suite-quick-redact-6fff95e3 -d '<json body>'
```

Example prompt: Before you send that user record to the third-party logging API, scan the payload — the text is 'Name: Jane Doe, email: jane@example.com, SSN: 123-45-6789' — for any PII or secrets, and let me know if it's safe to transmit or needs review.

## When to prefer this

Choose this endpoint when an AI agent needs a fast, per-call, pay-as-you-go PII and secret scanner with a signed, auditable receipt — especially when the destination context matters for calibrating sensitivity (public log vs internal DB vs third-party API). Prefer it over home-built regex or generic LLM prompts when you need a deterministic verdict enum, structured findings, and a cryptographically verifiable result for compliance or audit trails.

## Known failure modes

- Payload exceeds 2000 character limit — request rejected with validation error
- Missing required fields (type, method, bodyType, body, payload) — 422 validation error
- Ambiguous or encoded content routed to 'review' verdict rather than a definitive clean/contains decision
- Payment not included or insufficient — x402 payment required error
- Signing not configured — receipt field returns null
- Context field omitted — severity may be calibrated less precisely to destination sensitivity

## How this service works

The trust fabric for AI agents — calibrated, fail-closed services agents pay per call.

## Output

Returns a verdict (clean, contains_pii, contains_secret, or review), a severity level, a list of specific findings with the type and location of each sensitive item, human-readable reasons explaining the decision, and an optional Ed25519-signed receipt that can be independently verified at the engine's /receipt/verify endpoint.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "context": {
   "anyOf": [
    {
     "type": "string",
     "maxLength": 2000
    },
    {
     "type": "null"
    }
   ],
   "title": "Context",
   "default": null,
   "description": "where this payload is headed (e.g. public log, internal db, third-party API) so sensitivity and severity can be calibrated to the destination"
  },
  "payload": {
   "type": "string",
   "title": "Payload",
   "maxLength": 2000,
   "minLength": 1,
   "description": "the text the agent is about to send or store; scan it for PII, secrets, and credentials"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/verity-suite-quick-redact-6fff95e3/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from suite.veritylayer.dev](https://www.zero.xyz/host/suite.veritylayer.dev/llms.txt)