Pay-per-call employee SSN lookup via x402 on Base (USDC).
What it does
This endpoint at lowpaymentfee.com exposes an employee SSN (Social Security Number) retrieval API behind an x402 paywall. Calling POST to `/api/v1/employees/69/ssn` returns employee SSN data in JSON format after a USDC micropayment on the Base network. The x402 challenge confirms the endpoint is live and accepts exact-scheme payments.
The price per request is 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 USD (USDC uses 6 decimals). The provider's landing page advertises a flat $0.02/request pricing model across all endpoints, with no API keys, no rate limits, and instant access. Payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout.
The provider site lists many other endpoints across data/analytics, AI/ML, finance/Web3, and infrastructure categories, all at the same $0.02 price point. However, documentation is essentially nonexistent — the /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI spec, no request/response schema documentation, and no explanation of what data source backs the employee SSN endpoint. The nature of this endpoint — returning personally identifiable information (SSN) — raises significant regulatory and ethical concerns.
Capabilities
Use cases
- —Retrieving employee SSN data programmatically with per-call payment
- —Integrating employee identity verification into automated workflows
- —Accessing PII behind a crypto-paywall without API key management
Fit
Best for
- —Developers needing on-demand employee SSN data via micropayment
- —Agents that can settle x402 payments on Base in USDC
- —Use cases where keyless, pay-per-call access to data is preferred
Not for
- —Production systems requiring documented, auditable PII data sources
- —Applications subject to strict data privacy regulations (GDPR, CCPA, HIPAA) without clear compliance guarantees
- —Users who need detailed API documentation or schema validation before integration
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/employees/69/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/request in USDC on Base). However, there is zero documentation on request/response schemas, no OpenAPI spec, no examples, and the docs pages are empty. The endpoint deals with highly sensitive PII (SSN) with no stated compliance or data-source provenance, which is a major red flag.
Warnings
- —Endpoint returns Social Security Numbers — highly sensitive PII. No compliance documentation (HIPAA, CCPA, GDPR, SOC 2) is provided.
- —No documentation exists beyond the landing page; /docs, /api, /pricing, and /README all show only 'Connect wallet'.
- —No OpenAPI spec or request/response schema available — input and output formats are unknown.
- —Data source and legitimacy of employee SSN data are completely unverified.
- —The employee ID '69' is hardcoded in the URL path; it is unclear whether other IDs are supported or what the data represents.
- —Regulated data category: distributing SSNs may violate federal and state laws depending on jurisdiction and use case.
Citations
- —The x402 challenge returns maxAmountRequired of 20000 in USDC (asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Base networkhttps://lowpaymentfee.com/api/v1/employees/69/ssn
- —The provider advertises $0.02/request pricing with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —Documentation pages (/docs, /api, /pricing, /README) render only 'Connect wallet' with no technical contenthttps://lowpaymentfee.com/docs