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 (ID 175) behind an x402 paywall. The endpoint accepts POST requests and returns JSON. Payment is settled in USDC on the Base network at $0.02 per call (maxAmountRequired of 20,000 base units with 6 decimals = $0.02). No API keys or rate limits are required; access is gated entirely by the x402 payment protocol.
The provider site (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. Documentation pages exist but appear to require a wallet connection and contain no substantive content. There is no OpenAPI schema, no request/response examples, and no documentation describing the input parameters or output format for this specific endpoint. The endpoint path suggests it returns PII (a Social Security Number), which raises significant regulatory and ethical concerns.
The x402 challenge was successfully captured with a 402 response, confirming the endpoint is live. Payment is made to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 using USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Base. The timeout for payment settlement is 300 seconds.
Capabilities
Use cases
- —Retrieving employee SSN data for payroll or HR verification workflows
- —Programmatic access to sensitive employee identifiers behind a micropayment wall
- —Agent-driven identity verification requiring SSN data
Fit
Best for
- —Developers needing pay-per-call access to employee PII without API key management
- —Automated workflows that require SSN data and can settle payments in USDC on Base
- —Testing x402 payment protocol integrations with a live endpoint
Not for
- —Use cases requiring bulk employee data retrieval (single-employee endpoint)
- —Organizations that cannot handle PII in compliance with regulations like GDPR, CCPA, or SOX
- —Users who need detailed documentation or schema validation before integration
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/employees/175/ssn \
-H "X-PAYMENT: <x402-payment-header>" \
-H "Content-Type: application/json"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 parameters, response schema, or what data is actually returned. The endpoint purports to serve PII (SSN), which is a major regulatory red flag. No OpenAPI spec, no examples, and docs pages are empty beyond a wallet-connect prompt.
Warnings
- —Endpoint claims to return Social Security Number (SSN) data — this is highly sensitive PII subject to strict regulations (CCPA, GLBA, SOX, state breach notification laws). Verify legal compliance before use.
- —No documentation, OpenAPI schema, or example responses are available for this endpoint.
- —The endpoint path is hardcoded to employee ID 175; it is unclear whether other employee IDs are supported or how to parameterize requests.
- —All documentation pages on the provider site return only a 'Connect wallet' prompt with no substantive content.
- —Legitimacy of the data source is unverified — there is no indication of where the SSN data originates or whether it is real or synthetic.
Citations
- —Endpoint returns 402 with x402 challenge advertising USDC payment on Base networkhttps://lowpaymentfee.com/api/v1/employees/175/ssn
- —maxAmountRequired is 20000 base units of USDC (6 decimals) = $0.02https://lowpaymentfee.com/api/v1/employees/175/ssn
- —Provider site lists all APIs at $0.02 per request with no API keys, no rate limitshttps://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/employees/175/ssn