Retrieve employee SSN data via x402 micropayment on Base network for $0.02 per request.
What it does
This endpoint at lowpaymentfee.com returns employee Social Security Number (SSN) data for a specific employee record (ID 155) behind an x402 paywall. The endpoint accepts POST requests and is settled in USDC on the Base network. The x402 challenge advertises a maxAmountRequired of 20,000 base units of USDC (6 decimals), which equals $0.02 per request.
The provider lowpaymentfee.com hosts a broad catalog of pay-per-call APIs spanning data analytics, AI/ML inference, finance, and utility services, all priced at $0.02 per request with no API keys, no rate limits, and no commitments. However, this specific endpoint exposes what appears to be personally identifiable information (an employee's SSN), which raises significant regulatory and ethical concerns. No OpenAPI schema, request body documentation, or response examples were found in the crawled material — the docs, pricing, and API pages all returned only a "Connect wallet" prompt with no substantive content.
The endpoint is live and returns a valid x402 challenge (HTTP 402) with USDC payment details. Payment is directed to wallet 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 on Base, with a 300-second timeout. No input schema beyond HTTP POST is specified, and the output schema is not documented.
Capabilities
Use cases
- —Retrieving employee SSN data for payroll or HR integrations
- —Programmatic access to sensitive employee records behind a paywall
- —Agent-driven identity verification workflows requiring SSN data
Fit
Best for
- —Developers needing pay-per-call access to employee PII without API key management
- —Automated HR or payroll systems that need SSN lookups
- —x402-compatible agents on the Base network
Not for
- —Anyone without a legitimate, lawful need for SSN data — this endpoint exposes highly regulated PII
- —Use cases requiring documented request/response schemas or SLAs
- —High-volume bulk lookups where per-request pricing is inefficient
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/employees/155/ssn \
-H "X-PAYMENT: <x402_payment_token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but there is no documentation, no request/response schema, no examples, and the endpoint exposes highly sensitive PII (SSN) with no visible compliance or authorization framework. Docs pages returned only wallet-connect prompts.
Warnings
- —This endpoint exposes Social Security Numbers (PII), which is subject to strict legal regulation (e.g., GLBA, state privacy laws). Use with extreme caution and only where legally authorized.
- —No request body schema or response schema is documented anywhere in the crawled material.
- —All documentation pages (/docs, /api, /pricing, /README) returned only a 'Connect wallet' prompt with no substantive content.
- —The endpoint is hardcoded to employee ID 155 — it is unclear whether other employee IDs are supported or if this is a demo/test record.
- —No terms of service, privacy policy, or data handling documentation was found.
Citations
- —The x402 challenge advertises maxAmountRequired of 20000 base units of USDC on Base network with 300-second timeouthttps://lowpaymentfee.com/api/v1/employees/155/ssn
- —The provider advertises $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/employees/155/ssn