Retrieve employee SSN data via pay-per-request x402 endpoint on Base network.
What it does
This endpoint at lowpaymentfee.com returns employee Social Security Number (SSN) data for a specific employee record (employee ID 9) behind an x402 paywall. The endpoint accepts POST requests and returns JSON. Payment is settled in USDC on the Base network using the x402 "exact" scheme.
The price per request is $0.02 (20,000 base units of USDC with 6 decimals). No API keys or rate limits are required — callers simply attach an X-PAYMENT header with a valid x402 payment proof. The payment is directed to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a maximum timeout of 300 seconds.
The broader lowpaymentfee.com platform advertises multiple API categories (data/analytics, AI/ML, finance/Web3, infrastructure utilities), all priced at $0.02 per request. However, documentation is extremely sparse — the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no request/response examples, and no description of what fields are returned or what input the POST body expects. The specific nature of this endpoint — exposing SSN data — raises significant data sensitivity and regulatory concerns.
Capabilities
Use cases
- —Retrieving employee SSN for payroll or HR integrations
- —Programmatic identity verification workflows
- —Automated compliance checks requiring SSN data
Fit
Best for
- —Developers needing on-demand SSN retrieval without API key management
- —Agent-based workflows that can settle USDC payments on Base
- —Pay-per-use access to sensitive employee records
Not for
- —Bulk SSN lookups or batch processing (no documented batch endpoint)
- —Users without USDC on Base network
- —Applications requiring documented schemas, SLAs, or compliance certifications
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/employees/9/ssn \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_proof>"Endpoint
Quality
The endpoint is live (402 challenge captured) and pricing is clear ($0.02 USDC on Base), but there is zero documentation on request body format, response schema, or what data is actually returned. No OpenAPI spec, no examples, and the docs pages are empty. The SSN-specific nature raises serious regulatory red flags with no compliance information provided.
Warnings
- —Endpoint exposes Social Security Number data — highly sensitive PII subject to federal and state regulations (e.g., GLBA, state SSN protection laws). No compliance or authorization documentation is provided.
- —No request body schema or response schema documented anywhere. Callers must guess at the expected POST payload.
- —All documentation pages (docs, API, pricing, README) return only a 'Connect wallet' prompt with no usable content.
- —No OpenAPI specification or ai-plugin manifest available.
- —The endpoint path is hardcoded to employee ID 9; it is unclear whether other employee IDs are supported or how the broader employees API is structured.
Citations
- —Endpoint returns 402 with x402 challenge advertising USDC payment on Base network at 20000 base unitshttps://lowpaymentfee.com/api/v1/employees/9/ssn
- —Platform advertises $0.02 per request pricing with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/employees/9/ssn
- —Documentation pages render only 'Connect wallet' with no substantive contenthttps://lowpaymentfee.com/docs