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 135) 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 broader 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 be stubs (showing only a "Connect wallet" prompt with no further content). There is no OpenAPI schema, no request/response examples, and no detailed documentation for this specific endpoint. The actual data source behind the employee SSN endpoint is unknown — it is unclear whether this returns real, synthetic, or demo data.
The endpoint is live: the probe received a well-formed 402 challenge with x402 version 1, confirming the payment gateway is operational. The payment address is 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 and the USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 (Base mainnet USDC).
Capabilities
Use cases
- —Retrieving employee SSN data for payroll or HR integrations
- —Demonstrating x402 micropayment protocol for sensitive data access
- —Agent-driven lookups of employee PII behind a paywall
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents needing pay-per-call access to employee records
- —Scenarios requiring no-API-key, wallet-gated data access
Not for
- —Production PII lookups without verifying data source legitimacy and compliance
- —Bulk employee data retrieval (pay-per-request model, no batch endpoint documented)
- —Users without a Base-network USDC wallet
Quick start
# 1. Obtain an x402 payment header (via your x402 client library)
# 2. POST to the endpoint with the X-PAYMENT header
curl -X POST https://lowpaymentfee.com/api/v1/employees/135/ssn \
-H "X-PAYMENT: <your-x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live with a valid 402 challenge and clear pricing, but there is zero documentation on request parameters, response schema, or data provenance. The SSN/PII nature of the endpoint raises serious compliance and legitimacy concerns that are completely unaddressed. Docs pages are empty stubs.
Warnings
- —This endpoint claims to return Social Security Numbers (PII/sensitive data). The data source, legitimacy, and legal compliance are entirely unknown. Use extreme caution.
- —No documentation exists beyond the 402 challenge — no request schema, no response examples, no OpenAPI spec.
- —All documentation pages (/docs, /api, /pricing, /README) are empty stubs showing only 'Connect wallet'.
- —The endpoint path is hardcoded to employee ID 135; it is unclear if other IDs are supported or how the broader API works.
- —Handling of real SSNs may be subject to federal and state regulations (e.g., GLBA, state privacy laws). Verify compliance before use.
Citations
- —Endpoint returns 402 with x402 version 1 challenge, maxAmountRequired 20000 in USDC on Basehttps://lowpaymentfee.com/api/v1/employees/135/ssn
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/employees/135/ssn
- —All APIs priced at $0.02 per request with no API keys, no rate limitshttps://lowpaymentfee.com
- —Provider hosts additional API categories: Data & Analytics, AI & ML, Finance & Web3, Infrastructurehttps://lowpaymentfee.com