← Documentation

EVIDIQ Redact

Deterministic detection and removal of sensitive data — before an agent sends anything anywhere. Redact finds sensitive values by structure rather than by guesswork, removes them in the mode you choose, and returns a signed report of exactly what was found and where. No model in the hot path, and nothing is stored.

Listing under review

EVIDIQ Redact

Agent #9700

OKX.AI listing

https://www.okx.ai/agents/9700

Submitted for approval; the endpoint below is already live.

Open

MCP endpoint

https://mcp.evidiq.dev/redact/mcp

Streamable HTTP, x402-gated. Free tools answer without payment.

Quickstart

Connect the Streamable HTTP MCP endpoint, then preflight for free before paying.

claude mcp add --transport http evidiq-redact https://mcp.evidiq.dev/redact/mcp

Or probe the live pricing discovery endpoint:

curl -s https://mcp.evidiq.dev/redact/x402

Prefer a Skill file? Fetch the agent-readable EVIDIQ Redact Skill:

curl -s https://mcp.evidiq.dev/redact/skill.md

What Redact is for

Before a prompt

Strip customer records, credentials, and keys out of context before it reaches a model.

Checksum-validated detection

Luhn for cards, mod-97 for IBANs, wordlist plus checksum for BIP-39 mnemonics, EIP-55 for EVM addresses.

Credential interception

AWS, GitHub, OpenAI, Anthropic, Stripe keys and .env blocks by issuer shape.

Structure-preserving output

Markdown, HTML, CSV, JSON, NDJSON, and plain text keep their shape after redaction.

Policy verdicts

Versioned profiles return PASS, REVIEW, or BLOCK with the violations that caused it.

Zero retention

Content is processed in memory; artifacts live in a short-TTL cache addressed by digest.

Ten MCP tools

Five free tools cover discovery, preflight, and offline verification. Five paid tools handle detection, redaction, policy evaluation, and dataset de-identification.

Paid detection & redaction

Free preflight and verification

Engine limits

maxInputBytes

262144

artifactTtlMs

600000 (10 minutes, in memory)

detectorSetVersion

1.0.0 — 20 detectors

redactionModes

mask · label · hash · token · remove

Policy profiles: pii-basic, pci-lite, health-lite, crypto-hygiene, pre-prompt. Live values come from the free redact_capabilities tool.

Recommended workflow

Settlement happens before a paid tool runs, so a malformed argument is still a paid call. Preflight for free first.

  1. Call redact_capabilities for the detector set version, profiles, and prices.
  2. Call validate_input — it returns the finding count for free, so you can decide whether redaction is worth buying.
  3. Call estimate_cost for the intended operation.
  4. Submit one paid call per request. Redact enforces strict x402 payment authorization.
  5. Verify offline with verify_redaction_report, and re-fetch output with get_artifact while its TTL lasts.

What a report proves, and what it does not

A report proves that this exact input, under this detector set version and this policy version, produced this exact output and these findings. Anyone can re-run and compare digests. It does not prove the content is now free of sensitive data: deterministic detection has a recall limit, and unstructured personal names and postal addresses are the weak spot. They are reported at low confidence and can never alone drive a BLOCK.

Findings carry offsets and detector ids, never the matched values. A report that quoted what it found would itself be a leak, and reports get pasted into tickets.

{
  "engine": "EVIDIQ-Redact/1.0",
  "detectorSetVersion": "1.0.0",
  "policy": "pre-prompt",
  "findings": [
    { "detector": "BIP39_MNEMONIC", "family": "crypto_secret",
      "confidence": "validated", "start": 812, "end": 913, "action": "remove" }
  ],
  "verdict": "BLOCK",
  "integrity": { "algorithm": "SHA-256", "digest": "...", "signature": "0x...", "signer": "0x8a3c7524..." }
}

x402 pricing

ToolAtomicUSDT0Access
redact_text50000.005x402-paid
scan_document100000.01x402-paid
redact_document150000.015x402-paid
policy_check200000.02x402-paid
deidentify_dataset300000.03x402-paid
redact_capabilities0FreeAlways ungated
validate_input0FreeAlways ungated
estimate_cost0FreeAlways ungated
verify_redaction_report0FreeAlways ungated
get_artifact0FreeAlways ungated

Payments use x402 v2 exact scheme with USDT0 (6 decimals) on X Layer (eip155:196). The public discovery endpoint lists all ten tools.

Verification and settlement run through the official OKX Onchain OS Payment SDK (@okxweb3/x402-core and @okxweb3/x402-evm). The OKX facilitator verifies each authorization and settles it on X Layer before any detection runs. Each price reaches the SDK as an explicit USD₮0 atomic asset amount rather than a USD string, so neither the fee nor its token can be substituted by conversion.

Settled on X Layer

A live redact_text call paid 0.005 USDT0 (5000 atomic) on content carrying an email, a Luhn-valid card number, a BIP-39 mnemonic, and a private key. All four were detected, the verdict was BLOCK, every secret was removed from the output, and no matched value appeared in the report. The receipt is status 0x1 and the transaction was broadcast by an OKX facilitator relayer rather than a Redact-held key — the on-chain evidence that settlement ran through the official SDK. Test values were synthetic.

0x001261081770e0c9bc82a736a4a7e8739d25fe01ca578a445aa311f238e8efc4

Licensing

EVIDIQ owns and licenses its original Redact code under MIT. Third-party dependencies maintain their own open-source licenses preserved in THIRD_PARTY_NOTICES.md.

Redact inspects what an agent emits. For what an agent consumes, route endpoint and Agent Skill scanning to EVIDIQ Sentinel; for durable action logging, use EVIDIQ Vault. No compliance certification is claimed; policy profiles are engineering defaults, not legal advice.

← Back to docs