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 82) 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 x402 challenge advertises a maxAmountRequired of 20,000 base units of USDC (0x8335…2913 on Base, 6 decimals), which equals $0.02 per request. The provider's landing page confirms a flat $0.02/request pricing model across all their API endpoints, with no API keys, no rate limits, and instant access. The endpoint is live and returning a valid 402 challenge.
This endpoint is part of a broader platform (lowpaymentfee.com) that offers data & analytics, AI/ML, finance/Web3, and infrastructure utility APIs, all at the same $0.02 per-call price point. Documentation beyond the landing page is essentially empty (pages return only "Connect wallet" prompts), so there is no detailed schema or example response available for this specific endpoint. The nature of the data returned — employee SSN — raises significant privacy and regulatory concerns.
Capabilities
Use cases
- —Retrieving employee SSN for payroll or HR verification workflows
- —Programmatic access to sensitive employee identifiers behind a paywall
- —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 requiring SSN retrieval with crypto micropayments
- —x402-compatible agents on the Base network
Not for
- —Production systems requiring documented response schemas and SLAs
- —Use cases where handling SSN data would violate regulatory requirements (GDPR, state privacy laws)
- —Users who cannot transact in USDC on Base
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/employees/82/ssn \
-H "X-PAYMENT: <x402-payment-header>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge, but there is no documentation, no response schema, no example responses, and the docs/pricing/README pages are all blank. The endpoint serves highly sensitive PII (SSN) with no visible compliance or authorization framework, which is a major red flag.
Warnings
- —Endpoint returns employee Social Security Numbers — handling SSN data is subject to strict regulatory requirements (e.g., US state privacy laws, IRS Publication 1075, GLBA). Ensure compliance before use.
- —No documentation available — all doc pages return only 'Connect wallet' with no API schema, field descriptions, or example responses.
- —Endpoint is hardcoded to employee ID 82; it is unclear whether other employee IDs are supported or what the data source is.
- —No OpenAPI spec, no output schema beyond mimeType application/json. Response structure is entirely unknown.
- —Legitimacy of the data source is unverifiable from available materials.
Citations
- —The x402 challenge advertises maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/employees/82/ssn
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/employees/82/ssn
- —Provider landing page lists $0.02/request pricing with no API keys, no rate limits, instant accesshttps://lowpaymentfee.com