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 SSN (Social Security Number) data for a specific employee record (ID 136) behind an x402 paywall. Payment is settled in USDC on the Base network at $0.02 per request (maxAmountRequired of 20,000 base units with 6 decimals = $0.02). The endpoint uses the x402 "exact" payment scheme, meaning callers must attach a valid X-PAYMENT header to authorize a one-shot USDC transfer before receiving the response.
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 with no API keys, no rate limits, and no commitments. However, this specific endpoint serves sensitive personally identifiable information (an employee's SSN), which raises significant regulatory and ethical concerns. The endpoint is live and returns a proper 402 challenge, but documentation beyond the landing page is essentially empty (all subpages just show "Connect wallet"), so there is no schema documentation for request parameters or response format.
Capabilities
Use cases
- —Retrieving employee SSN for internal HR or payroll integrations
- —Programmatic identity verification workflows requiring SSN data
- —Agent-driven compliance checks that need SSN cross-referencing
Fit
Best for
- —Developers needing pay-per-call access to employee PII without subscription overhead
- —Automated agents that can settle USDC payments on Base L2
- —Low-volume, on-demand SSN lookups
Not for
- —Bulk PII harvesting or scraping — no documented batch endpoint
- —Use cases where handling SSN data would violate privacy regulations (GDPR, CCPA, etc.)
- —Users who cannot transact in USDC on the Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/employees/136/ssn \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02 USDC on Base), but there is zero documentation on request/response schemas, no OpenAPI spec, and the docs/pricing/API pages are all blank. The endpoint serves highly sensitive PII (SSN) with no visible compliance or authorization framework documented.
Warnings
- —This endpoint serves Social Security Numbers — highly regulated PII. Ensure compliance with all applicable privacy laws (CCPA, GLBA, etc.) before use.
- —No documentation exists for request body schema or response format; all doc pages return only 'Connect wallet'.
- —No OpenAPI or machine-readable schema is available.
- —The endpoint path is hardcoded to employee ID 136; it is unclear whether other employee IDs are supported or how the broader API is parameterized.
- —Provider legitimacy and data sourcing are unverified — exercise extreme caution with any PII endpoint.
Citations
- —Endpoint returns 402 with x402 challenge, maxAmountRequired 20000 in USDC on Base networkhttps://lowpaymentfee.com/api/v1/employees/136/ssn
- —All APIs priced at $0.02 per request with no API keys, no rate limits, instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/employees/136/ssn
- —Documentation pages (docs, api, pricing, README) contain no substantive contenthttps://lowpaymentfee.com/docs