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 (employee ID 19). It is part of a broader suite of x402-protocol pay-per-call APIs hosted on the same domain, all settling payments in USDC on the Base L2 network.
The endpoint is live and responds with a standard x402 payment challenge (HTTP 402) requiring an X-PAYMENT header. The price is 20,000 base units of USDC (0x8335…2913 on Base), which at 6 decimals equals $0.02 per request. The payment scheme is "exact" with a 300-second timeout. The endpoint accepts POST requests and returns application/json.
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. However, the docs, pricing, and README pages all returned only a "Connect wallet" prompt with no substantive documentation. There is no OpenAPI spec, no request/response schema documentation, and no explanation of what fields the response contains or what input the POST body expects. The nature of the data (SSN) raises significant regulatory and ethical concerns — exposing personally identifiable information (PII) of this sensitivity through a pay-per-call API with no authentication or access controls is a major red flag.
Capabilities
Use cases
- —Retrieving employee SSN data for a specific employee record
- —Demonstrating x402 micropayment protocol integration
- —Testing pay-per-call API patterns on Base network
Fit
Best for
- —Developers testing x402 payment protocol flows
- —Exploring micropayment-gated API patterns
Not for
- —Production use involving real PII — regulatory compliance (GDPR, CCPA, SOX) is unclear
- —Any use case requiring documented request/response schemas
- —Applications needing authentication, audit trails, or access controls for sensitive data
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/employees/19/ssn \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live (402 challenge captured) and pricing is clear ($0.02 USDC on Base), but there is zero documentation on request format, response schema, or data provenance. The docs/pricing/README pages are all empty. The sensitive nature of the data (SSN) with no visible compliance or access controls is a serious concern. Effectively a stub listing.
Warnings
- —Endpoint exposes Social Security Number (SSN) data — highly sensitive PII with significant regulatory implications (HIPAA, CCPA, GDPR, SOX). Use with extreme caution.
- —No documentation available: docs, pricing, and README pages all return only a wallet-connect prompt with no content.
- —No OpenAPI spec or response schema provided — request body format and response fields are unknown.
- —No authentication or access controls beyond payment — anyone who pays $0.02 can access the data.
- —Data provenance is entirely unknown — it is unclear whether this is real, synthetic, or demo data.
Citations
- —Endpoint returns HTTP 402 with x402 challenge requiring USDC payment on Basehttps://lowpaymentfee.com/api/v1/employees/19/ssn
- —Price is 20000 base units of USDC (asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913), equal to $0.02https://lowpaymentfee.com/api/v1/employees/19/ssn
- —Provider advertises $0.02/request flat pricing with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —Docs, pricing, and README pages contain only a 'Connect wallet' prompt with no substantive contenthttps://lowpaymentfee.com/docs