Anonymize sensitive information in text via x402-paid API on Base network.
What it does
This endpoint accepts JSON input containing text and anonymizes sensitive information (PII) using a configurable provider such as Azure AI Language. It is hosted on SlinklyLayer's x402 proxy infrastructure and settles payments in USDC on the Base network.
The API expects a POST request with a JSON body containing the text to anonymize, a language code, a requested_service identifier, and optionally Azure credentials (key and endpoint) if using Azure as the anonymization provider. The x402 payment challenge indicates a maximum cost of $0.05 per request (50,000 base units of USDC with 6 decimals). Payment is made via the x402 exact scheme to the specified wallet address.
Documentation beyond the x402 challenge itself is minimal — the provider's site returns only "Hello, world!" at the root and 404 on /docs, /api, /pricing, and /README. The output schema embedded in the challenge provides the only available field-level documentation. The required fields are `language` (string) and `requested_service` (string), while `text` (string) and `azure` (object with `key` and `endpoint`) are optional. Without further docs it is unclear what values `requested_service` accepts or what providers besides Azure are supported.
Capabilities
Use cases
- —Stripping personally identifiable information from user-submitted text before storage or analysis
- —Anonymizing medical or legal documents for compliance with privacy regulations
- —Pre-processing text data to remove PII before feeding into LLMs or analytics pipelines
- —Redacting sensitive fields in customer support transcripts
Fit
Best for
- —Developers needing on-demand PII anonymization without managing their own NLP infrastructure
- —Pipelines that require pay-per-call text anonymization settled in crypto
- —Applications that already use Azure AI Language and want a payment-gated proxy
Not for
- —High-volume batch anonymization where per-call crypto payments add overhead
- —Use cases requiring detailed audit logs or compliance certifications from the proxy layer
- —Users who need comprehensive documentation or SLA guarantees
Quick start
curl -X POST https://x402.slinkylayer.ai/api/v1/proxy/2ce94988-5413-4458-bac6-5c523d998dc5/text-anonymize \
-H 'Content-Type: application/json' \
-H 'X-PAYMENT: <x402_payment_header>' \
-d '{"text": "John Doe lives at 123 Main St.", "language": "en", "requested_service": "azure"}'Example
Request
{
"text": "John Doe lives at 123 Main St and his email is john@example.com.",
"azure": {
"key": "YOUR_AZURE_KEY",
"endpoint": "https://your-resource.cognitiveservices.azure.com"
},
"language": "en",
"requested_service": "azure"
}Endpoint
Quality
The endpoint is live and returns a valid x402 challenge with an embedded outputSchema describing the request body fields. However, there is no external documentation, no response schema, no example responses, and the provider site is essentially empty. Field semantics (e.g., valid values for requested_service) must be guessed.
Warnings
- —No documentation available — /docs, /api, /pricing, /README all return 404.
- —Provider landing page is a bare 'Hello, world!' with no information about the service.
- —Response schema is unknown; example_response_json is null.
- —Valid values for 'requested_service' and supported providers beyond Azure are undocumented.
- —The 'text' field is marked as not required in the schema, which is unexpected for a text anonymization endpoint — may indicate schema inaccuracy.
Citations
- —The endpoint returns a 402 challenge with x402Version 1 and accepts USDC on Base network.https://x402.slinkylayer.ai/api/v1/proxy/2ce94988-5413-4458-bac6-5c523d998dc5/text-anonymize
- —Maximum amount required is 50000 base units of USDC (asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913), equating to $0.05.https://x402.slinkylayer.ai/api/v1/proxy/2ce94988-5413-4458-bac6-5c523d998dc5/text-anonymize
- —The outputSchema specifies required fields 'language' and 'requested_service', and optional fields 'text' and 'azure'.https://x402.slinkylayer.ai/api/v1/proxy/2ce94988-5413-4458-bac6-5c523d998dc5/text-anonymize
- —Provider root page returns 'Hello, world!' with HTTP 200.https://x402.slinkylayer.ai