{"uid":"cap_ge_HGDqHbmB33CTr7Q7fY","slug":"verity-suite-pii-secret-redaction-pro-c9b4af23","name":"Verity Suite — PII & Secret Redaction (Pro)","description":"The trust fabric for AI agents — calibrated, fail-closed services agents pay per call.","url":"https://suite.veritylayer.dev/redact/pro","method":"POST","headers":{},"bodySchema":{"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"}}},"responseSchema":null,"example":null,"exampleRequest":null,"tags":["x402"],"displayCostAmount":"0.15","displayCostAsset":"USDC","priceDynamic":false,"priceHint":null,"priceStatus":"priced","priceSource":"probe","requiresHandshake":false,"reviewCount":0,"rating":{"score":"0.00","successRate":"0.00","reviews":0,"stars":null,"state":"unrated"},"availabilityStatus":"unknown","priceObserved":null,"sessionDeposit":null,"pricing":{"kind":"static","summary":"$0.15/call","primary":{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.15","per":"call","confidence":"exact"},"accepted":[{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.15","per":"call","confidence":"exact"}]},"paymentMethods":[{"uid":"pm_Y_0HLxrcZTSanfsosWBlY","protocol":"x402","methodType":"crypto","chain":"base","mode":"charge","costAmount":"0.15","costPer":"request","priority":0,"asset":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913","unit":"request","depositMicros":null,"planRef":null}],"brandName":null,"brandSlug":null,"brandBaseUrl":null,"brandDocsUrl":null,"whatItDoes":"Scans text payloads for PII, secrets, and credentials before they are sent or stored, returning a signed verdict and structured findings with severity","exampleAgentPrompt":"Before you POST this customer record to our analytics API, scan it for any PII, secrets, or credentials — I need a signed verdict and the specific findings so I know it's safe to send.","exampleUseCases":[{"title":"Pre-send privacy gate for outbound API calls","prompt":"Before sending that payload to the third-party CRM, scan it for any personal data like names, emails, or phone numbers — I need to know the verdict and severity before it leaves our system."},{"title":"Secret leak prevention in agent-generated code","prompt":"Check this agent-generated config snippet for any hardcoded API keys, tokens, or credentials before it gets committed to the repo — flag exactly what you find and how serious it is."},{"title":"Compliance check before writing to a public audit log","prompt":"Scan this transaction summary for PII or sensitive identifiers before we write it to the public audit log — I need a signed receipt I can keep as proof it was reviewed."}],"resultDescription":"Returns a JSON object with: a verdict enum (clean, contains_pii, contains_secret, or review), a severity level, an array of structured findings identifying what was detected and where, an array of human-readable reasons explaining the routing decision, and an optional Ed25519-signed VerityLayer receipt that can be independently verified at the engine's POST /receipt/verify endpoint. The receipt is null if signing is not configured.","failureModes":["Payload exceeds 2000 character limit — returns validation error","Missing required fields (type, method, bodyType, body, payload) — returns 422 schema error","Ambiguous or encoded content routed to 'review' verdict rather than a definitive clean/flagged decision","Payment not included or insufficient — returns 402 Payment Required","Service unavailable or timeout — fail-closed behavior expected given trust-critical nature"],"whenToPreferThis":"Choose this endpoint when an AI agent needs a calibrated, fail-closed PII and secret scanner with a cryptographically signed audit receipt — especially for compliance-sensitive pipelines where you need proof of review, destination-aware sensitivity calibration, or detection of embedded prompt injection directives in outbound payloads. Prefer it over generic regex filters when you need structured findings with severity, human-readable reasons, and a verifiable chain of custody.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-09-14T12:32:10.854Z","isFirstParty":false}