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 176) 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/response examples, or detailed documentation were found beyond the x402 challenge itself and the provider's landing page.
The endpoint is live and returns a proper 402 challenge. Payment is made via the x402 "exact" scheme to wallet 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 using USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Base. The response MIME type is application/json. No input schema or response schema details are documented.
Capabilities
Use cases
- —Retrieving employee SSN for authorized payroll or HR integrations
- —Programmatic access to sensitive employee records behind a paywall
- —Agent-driven identity verification workflows (with proper authorization)
Fit
Best for
- —Developers needing pay-per-call access to employee PII without API key management
- —Automated HR or payroll systems requiring SSN data
- —x402-compatible agents on the Base network
Not for
- —Unauthorized access to personal data — SSN retrieval has strict legal requirements (FCRA, GLBA, state privacy laws)
- —Bulk data scraping or mass PII collection
- —Use cases where regulatory compliance (SOC 2, HIPAA) requires auditable access controls beyond a simple paywall
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/employees/176/ssn \
-H "X-PAYMENT: <x402_payment_token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge, but there is no OpenAPI schema, no documented request/response format, no examples, and the docs pages are empty stubs. The endpoint exposes PII (SSN), which is a major regulatory red flag with no indication of compliance controls.
Warnings
- —This endpoint appears to serve personally identifiable information (Social Security Numbers). Accessing, storing, or transmitting SSNs is heavily regulated under US federal and state law (FCRA, GLBA, state breach notification laws). Use with extreme caution and proper legal review.
- —No documentation, request schema, or response schema is available beyond the x402 challenge metadata.
- —The provider's docs, pricing, API, and README pages all render only a 'Connect wallet' prompt with no substantive content.
- —It is unclear whether this is real employee data or synthetic/demo data. The endpoint path references a specific employee ID (176), suggesting it may be a demo or test fixture.
- —No authentication or authorization mechanism beyond payment is documented — a payment-only gate on SSN data is unusual and potentially non-compliant.
Citations
- —The x402 challenge advertises maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/employees/176/ssn
- —All APIs on the platform are priced at $0.02 per request with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/employees/176/ssn
- —Payment recipient wallet is 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3https://lowpaymentfee.com/api/v1/employees/176/ssn