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 71) 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, with a maximum cost of $0.02 per request (20,000 base units of USDC with 6 decimals).
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 deals with sensitive personally identifiable information (employee SSN), which raises significant regulatory and ethical concerns. No documentation, input schema, or example responses are available beyond the x402 challenge and the landing page listing.
The endpoint is live and returns a proper 402 challenge. The payment address is 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 and the USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base. The x402 version is 1 with a maximum timeout of 300 seconds.
Capabilities
Use cases
- —Retrieving employee SSN for payroll or HR integrations
- —Automated identity verification workflows requiring SSN data
- —Agent-driven compliance checks needing employee identifiers
Fit
Best for
- —Programmatic access to employee SSN data without API key management
- —Pay-per-use access to sensitive employee records
- —x402-compatible agents on Base network
Not for
- —Bulk data scraping of PII — no batch endpoint documented
- —Use cases where handling SSNs would violate data protection regulations (GDPR, CCPA, etc.)
- —Users who need detailed documentation or schema guarantees before integration
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/employees/71/ssn \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-header>"Endpoint
Quality
The endpoint is live and returns a valid 402 challenge, but there is no OpenAPI schema, no documentation, no example request/response, and the endpoint serves highly sensitive PII (SSN) with no visible compliance or authorization framework. The crawled docs/pricing/API pages are all blank beyond a wallet-connect prompt.
Warnings
- —This endpoint exposes Social Security Numbers (PII). Consuming or reselling SSN data may violate federal and state privacy laws (e.g., CCPA, GLBA, FCRA). Verify legal compliance before use.
- —No input schema or response schema is documented — the actual data returned is unknown.
- —Documentation pages (/docs, /api, /pricing, /README) are effectively empty, showing only a 'Connect wallet' prompt.
- —The legitimacy and data source of the employee SSN data is unverified. This could be synthetic/demo data or potentially illicit.
- —Only a single employee ID (71) is referenced in this endpoint path; it is unclear if other IDs are supported.
Citations
- —Endpoint returns HTTP 402 with x402 challenge advertising USDC payment on Basehttps://lowpaymentfee.com/api/v1/employees/71/ssn
- —Provider advertises $0.02 per request pricing with no API keys, no rate limitshttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/employees/71/ssn
- —Payment address is 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3https://lowpaymentfee.com/api/v1/employees/71/ssn