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 163) 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 site also offers endpoints in categories like data analytics, AI/ML inference, finance/Web3, and infrastructure utilities — all at the same price point.
Documentation is extremely sparse. The /docs, /api, /pricing, and /README pages all returned only a "Connect wallet" prompt with no further content. There is no OpenAPI spec, no request/response schema documentation, and no explanation of what fields the SSN endpoint actually returns or what input it expects beyond a POST to the given URL. The endpoint is live (returns a valid 402 challenge), but the nature of the data — purporting to be an employee SSN — raises significant regulatory and ethical concerns.
Capabilities
Use cases
- —Retrieving employee SSN data for payroll or HR integrations
- —Programmatic access to sensitive employee identifiers
- —Agent-driven lookups of employee PII with per-call payment
Fit
Best for
- —Developers needing on-demand SSN retrieval without API key management
- —Automated systems requiring pay-per-call access to employee records
- —x402-compatible agents on the Base network
Not for
- —Anyone without a legitimate, lawful need for SSN data — exposing SSNs raises serious privacy and compliance risks
- —Use cases requiring bulk data export or batch processing (no documented batch endpoint)
- —Users who need detailed documentation or guaranteed SLAs
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/employees/163/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 documentation is effectively nonexistent — no OpenAPI spec, no request/response schema, no examples. The endpoint purports to serve highly sensitive PII (SSNs) with no visible compliance, authentication, or authorization controls beyond payment. This is a stub-level listing with serious regulatory red flags.
Warnings
- —Endpoint claims to return Social Security Numbers — this is highly regulated PII (subject to FCRA, state privacy laws, GDPR-adjacent rules). Use with extreme caution and only where legally authorized.
- —No documentation exists beyond the landing page listing. /docs, /pricing, /api, and /README all return only a wallet-connect prompt.
- —No OpenAPI spec or response schema is available; request body format and response structure are unknown.
- —No information on data provenance — it is unclear whether the SSN data is real, synthetic, or a demo placeholder.
- —The endpoint path is hardcoded to employee ID 163; it is unclear if other employee IDs are supported.
Citations
- —The x402 challenge advertises maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/employees/163/ssn
- —The provider advertises $0.02 per request pricing with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —The USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/employees/163/ssn
- —Documentation pages (/docs, /api, /pricing, /README) returned only a Connect wallet prompt with no substantive contenthttps://lowpaymentfee.com/docs