Detect and redact PII in text: find and mask names, addresses, SSNs, emails, and phone numbers. POST /v1/pii with {text} and get findings and masked output as one JSON object. Deterministic per ruleset version. Pay per request in USDC; no account, no API key.
POST https://agent.pocket.network/v1/pii-redaction/v1/piiThe first call returns 402 Payment Required with the terms. Sign for those terms and retry the same request with the payment attached.
A real, working call — the request the service card verifies against.
curl -X POST https://agent.pocket.network/v1/pii-redaction/v1/pii \
-H 'content-type: application/json' \
-d '{"text":"Email bob@example.com or call 555-123-4567."}'The response this call returned, captured 2026-09-21 23:48:44 UTC.
{
"portal": {
"provenance": "third-party-supplier",
"serviceId": "pii-redaction",
"schemaCheck": "unchecked"
},
"data": {
"redacted": "Email [EMAIL] or call [PHONE].",
"findings": {
"EMAIL": 1,
"PHONE": 1
},
"total": 2,
"ruleset": "pii-rules-v1.2",
"deterministic": true,
"as_of": "2026-09-21"
}
}Make one real paid call from your own wallet — about $0.005 on Base (eip155:8453). The wallet signs; nothing here holds a key. You'll see exactly what the service answers.
Methods the registry lists for this service. The portal forwards any call as sent; the supplier decides what it answers, and a delivered answer is settled.
| Method | Effect |
|---|---|
GET /v1/health | read |
GET /v1/version | read |
POST /v1/pii | read |
Published by the service itself. The example above is generated from these.
{
"type": "object",
"description": "Text to scan and redact.",
"properties": {
"text": {
"type": "string",
"description": "The text to inspect for PII."
}
},
"required": [
"text"
]
}{
"type": "object",
"description": "For POST /v1/pii, a JSON object with a `findings` array and the masked text. The exact shape is the service's own and is not pinned here; errors return a JSON object with an `error` field, and the GET routes return their own small JSON documents."
}