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 169) behind an x402 paywall. The endpoint accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x8335…2913) with a maximum amount of 20,000 base units, which equals $0.02 USD (USDC uses 6 decimals). No API keys or rate limits are required — access is gated purely by the x402 payment protocol.
The provider site (lowpaymentfee.com) hosts a broad catalog of x402-gated APIs spanning data analytics, AI/ML inference, finance, and utility endpoints, all priced at $0.02 per request. Documentation pages exist but appear to be stubs (returning 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 endpoint path suggests it returns personally identifiable information (an SSN), which raises significant regulatory and ethical concerns.
The x402 challenge was successfully captured (HTTP 402 with valid accepts block), confirming the endpoint is live. However, the lack of any documentation, input schema, or sample responses means the actual behavior and data source behind this endpoint are unknown. Callers should exercise extreme caution given the sensitive nature of SSN data.
Capabilities
Use cases
- —Retrieving SSN data for employee ID 169 via programmatic payment
- —Demonstrating x402 protocol micropayment flows
- —Accessing sensitive employee records without traditional API key authentication
Fit
Best for
- —Developers exploring x402 payment protocol mechanics
- —Agents needing pay-per-call access without signup
Not for
- —Production PII handling without compliance review
- —Bulk employee data retrieval (endpoint is scoped to a single employee ID)
- —Use cases requiring documented request/response schemas
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/employees/169/ssn \
-H "X-PAYMENT: <x402_payment_token>" \
-H "Content-Type: application/json"Endpoint
Quality
The x402 challenge is live and pricing is clear ($0.02 USDC on Base), but there is zero documentation, no request/response schema, no examples, and the endpoint exposes what appears to be highly sensitive PII (SSN) with no compliance or data-source information. All doc pages are stubs.
Warnings
- —Endpoint appears to serve personally identifiable information (Social Security Numbers) — significant regulatory risk (FCRA, state privacy laws, GDPR if applicable).
- —No documentation, input schema, or response examples are available; all doc pages return only a wallet-connect stub.
- —Data provenance is unknown — it is unclear whether this returns real, synthetic, or placeholder SSN data.
- —Endpoint is scoped to a single hardcoded employee ID (169); unclear if other IDs are supported via different URLs.
- —No OpenAPI spec or ai-plugin manifest found.
Citations
- —x402 challenge returns 402 with USDC on Base, maxAmountRequired 20000 (=$0.02)https://lowpaymentfee.com/api/v1/employees/169/ssn
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/employees/169/ssn
- —Site advertises $0.02/request pricing with no API keys, no rate limits, instant access on Base networkhttps://lowpaymentfee.com
- —Documentation pages return only a Connect wallet stub with no further contenthttps://lowpaymentfee.com/docs