Retrieve employee SSN data via x402 micropayment on Base network for $0.02 per request.
What it does
This endpoint at lowpaymentfee.com returns Social Security Number (SSN) data for a specific employee (ID 170) behind an x402 paywall. It accepts POST requests and settles payments in USDC on the Base network. The x402 challenge advertises a maxAmountRequired of 20,000 base units of USDC (6 decimals), which equals $0.02 per request.
The provider site lowpaymentfee.com hosts a broad catalog of x402-gated APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services — all priced at $0.02 per call with no API keys, no rate limits, and no commitments. However, this specific endpoint exposes personally identifiable information (an employee's SSN), which raises significant regulatory and ethical concerns. No documentation, request/response schemas, or usage examples are provided beyond the x402 challenge itself.
The endpoint is live and returns a proper 402 challenge. Payment is made via the x402 "exact" scheme to wallet 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 using USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Base. The timeout is 300 seconds. No OpenAPI spec, input schema, or response schema was found.
Capabilities
Use cases
- —Retrieving SSN for a specific employee record behind a paywall
- —Programmatic access to sensitive employee data for authorized HR systems
- —Demonstrating x402 micropayment gating on sensitive data endpoints
Fit
Best for
- —Authorized systems needing on-demand SSN retrieval with per-call billing
- —Developers exploring x402 payment protocol integration
- —Scenarios where API-key-free access to gated data is preferred
Not for
- —Unauthorized access to personally identifiable information
- —Any use that violates privacy regulations (GDPR, CCPA, HIPAA, etc.)
- —Production systems requiring documented schemas and SLAs
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/employees/170/ssn \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but there is no documentation, no request/response schema, no examples, and the endpoint exposes highly sensitive PII (SSN) with no visible authorization or compliance framework. Significant regulatory red flags.
Warnings
- —This endpoint exposes Social Security Numbers (PII) — use may violate GDPR, CCPA, HIPAA, or other privacy regulations.
- —No documentation, OpenAPI spec, or response schema is available.
- —No input parameters are documented; it is unclear what POST body (if any) is expected.
- —The endpoint is hardcoded to employee ID 170 — unclear if other IDs are supported.
- —No visible compliance, authorization, or access-control framework beyond the payment gate.
- —The broader site appears to be a demo/showcase with minimal real documentation (most pages just show 'Connect wallet').
Citations
- —The x402 challenge advertises maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/employees/170/ssn
- —USDC contract address is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/employees/170/ssn
- —All APIs on the site are priced at $0.02 per request with no API keys, no rate limitshttps://lowpaymentfee.com
- —Payment timeout is 300 secondshttps://lowpaymentfee.com/api/v1/employees/170/ssn