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 149) behind an x402 paywall. The endpoint accepts POST requests and is settled in USDC on the Base network. The x402 challenge confirms the endpoint is live and requires a payment of 20,000 base units of USDC (0.02 USD, since USDC uses 6 decimals) per request.
The provider site lowpaymentfee.com hosts a broad catalog of pay-per-call APIs spanning data analytics, AI/ML inference, finance, and utility services, all priced at $0.02 per request with no API keys, no rate limits, and no commitments. However, this specific endpoint — `/api/v1/employees/149/ssn` — is not listed among the advertised API categories on the landing page, and no documentation, request schema, or response schema is available for it. The endpoint's purpose (returning an SSN for a hardcoded employee ID) raises significant questions about the nature and legitimacy of the data being served. There is no documentation explaining what data source backs this endpoint or whether the data is synthetic, test/demo data, or real PII.
Because no OpenAPI spec, request body schema, or response example is provided, the actual behavior of this endpoint after payment is unknown. Callers should exercise extreme caution given the sensitive nature of SSN data and the complete lack of documentation around data provenance, compliance, or authorization.
Capabilities
Use cases
- —Retrieving employee SSN data for authorized internal systems
- —Testing x402 payment flows with a sample endpoint
- —Demonstrating pay-per-call micropayment patterns
Fit
Best for
- —Developers testing x402 payment protocol integrations
- —Internal tools needing programmatic SSN access with payment gating
Not for
- —Any use involving unauthorized access to real personal data
- —Production PII lookups without verified compliance and data provenance
- —Users needing documented, well-specified API contracts
Quick start
# This endpoint requires an x402 payment header (USDC on Base, $0.02).
# First, obtain the 402 challenge, then construct the X-PAYMENT header.
curl -X POST https://lowpaymentfee.com/api/v1/employees/149/ssn \
-H 'Content-Type: application/json' \
-H 'X-PAYMENT: <signed-payment-token>'Endpoint
Quality
The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02 USDC on Base), but there is zero documentation, no request/response schema, no examples, and the endpoint is not listed on the provider's own landing page. The sensitive nature of SSN data with no provenance or compliance information is a major red flag.
Warnings
- —Endpoint serves SSN (Social Security Number) data — highly regulated PII category. No documentation on data provenance, authorization model, or compliance (e.g., FCRA, GLBA, state privacy laws).
- —This specific endpoint is NOT listed among the provider's advertised APIs on the landing page, raising questions about its legitimacy or intended audience.
- —No request body schema, response schema, or usage examples are available anywhere in the crawled material.
- —All documentation, pricing, API, and README pages returned only 'Connect wallet' with no substantive content.
- —Data may be synthetic/demo — impossible to verify without further information from the provider.
Citations
- —The x402 challenge returns maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/employees/149/ssn
- —USDC asset address 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/employees/149/ssn
- —Provider advertises $0.02 per request, no API keys, no rate limitshttps://lowpaymentfee.com
- —This specific employee SSN endpoint is not listed among the provider's advertised API categorieshttps://lowpaymentfee.com