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 76). It is part of a broader platform offering various pay-per-request APIs across data analytics, AI/ML, finance, and utility categories, all settled via the x402 protocol on the Base network using USDC.
The endpoint accepts POST requests and returns JSON. Payment is handled inline via the x402 protocol: callers attach an X-PAYMENT header with a signed USDC payment on Base. The maximum amount required per call is 20,000 base units of USDC (0.02 USD, since USDC uses 6 decimals). The payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a timeout of 300 seconds.
The platform advertises no API keys, no rate limits, and instant access. Documentation pages beyond the landing page appear to require a wallet connection and contain no additional readable content. There is no OpenAPI schema, no request/response examples, and no detailed documentation available for this specific endpoint. The nature of the data returned (employee SSN) raises significant regulatory and privacy concerns — SSNs are highly sensitive personally identifiable information (PII) subject to strict legal protections in the United States.
Capabilities
Use cases
- —Retrieving employee SSN for authorized payroll or HR integrations
- —Programmatic access to sensitive employee records with per-call payment
- —Automated identity verification workflows requiring SSN data
Fit
Best for
- —Developers needing pay-per-call access to employee PII without API key management
- —x402-compatible agents on Base network seeking data endpoints
- —Scenarios where per-request billing is preferred over subscription models
Not for
- —Unauthorized access to PII — SSN data is legally protected and misuse carries severe penalties
- —Production systems requiring detailed API documentation, SLAs, or compliance certifications
- —Users without USDC on Base network or x402-compatible payment infrastructure
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/employees/76/ssn \
-H "X-PAYMENT: <x402-signed-payment-header>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02 USDC on Base), but there is no OpenAPI schema, no request/response examples, no documentation beyond a landing page, and the endpoint serves highly sensitive PII (SSN) with no visible compliance or authorization framework. The docs pages all render as just 'Connect wallet' with no usable content.
Warnings
- —This endpoint claims to serve Social Security Numbers (SSNs), which are highly sensitive PII regulated under US federal and state laws. Accessing, storing, or transmitting SSNs without proper authorization may violate laws including the Privacy Act, GLBA, HIPAA, and state data breach notification statutes.
- —No documentation, request schema, or response schema is available — the endpoint's actual behavior and data authenticity cannot be verified.
- —The legitimacy and legality of this data source is unverified. This may be a demonstration/dummy endpoint rather than a real PII source.
- —All documentation pages beyond the landing page returned only 'Connect wallet' with no readable content.
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/employees/76/ssn
- —The platform advertises $0.02 per request pricing with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —USDC asset address 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base networkhttps://lowpaymentfee.com/api/v1/employees/76/ssn
- —Payment recipient is 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with 300 second timeouthttps://lowpaymentfee.com/api/v1/employees/76/ssn