Retrieve employee SSN data via x402 micropayment on Base network for $0.02 per request.
What it does
This x402-enabled endpoint at lowpaymentfee.com returns employee SSN (Social Security Number) data for a specific employee record (ID 199). It is part of a broader suite of pay-per-request APIs offered by the same provider, spanning data analytics, AI/ML inference, finance, and utility services. All endpoints on the platform use the x402 payment protocol, settling in USDC on the Base network.
The endpoint accepts POST requests and returns JSON. The x402 challenge confirms the endpoint is live, requiring a maximum payment of 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 USD (USDC uses 6 decimals). No API keys or rate limits are advertised — access is gated purely by the x402 micropayment. The payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout.
Documentation is extremely sparse. The provider's docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI schema, no request/response examples, and no description of what fields the response contains beyond the path implying it returns an SSN for employee 199. The nature of the underlying data (real, synthetic, or demo) is entirely unknown. Given that this endpoint purports to return Social Security Numbers, users should exercise extreme caution regarding data authenticity, legality, and regulatory compliance.
Capabilities
Use cases
- —Retrieving employee SSN data on a per-request payment basis
- —Demonstrating x402 micropayment protocol integration
- —Testing pay-per-request data access patterns on Base network
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Testing micropayment-gated API workflows
- —Exploring pay-per-request data access without API keys
Not for
- —Production use requiring verified, authoritative SSN data
- —Applications subject to PII regulations (GDPR, CCPA, HIPAA) without due diligence on data provenance
- —Users who need detailed API documentation or schema guarantees
Quick start
# Requires an x402-compatible client to attach payment header
curl -X POST https://lowpaymentfee.com/api/v1/employees/199/ssn \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_token>"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 no information about data provenance. The endpoint claims to return SSN data, which raises serious regulatory concerns with no explanation from the provider.
Warnings
- —Endpoint purports to return Social Security Numbers — data authenticity and legality are completely unknown
- —No API documentation, OpenAPI schema, or response examples available
- —All doc/pricing/README pages return only 'Connect wallet' with no content
- —Hardcoded employee ID 199 in the path — unclear if other IDs are supported
- —Sensitive PII category — regulatory compliance (FCRA, CCPA, GDPR) must be independently verified
- —Data may be synthetic/demo; no provider disclosure available
Citations
- —The endpoint returns a 402 challenge requiring USDC payment on Base network with maxAmountRequired of 20000 base unitshttps://lowpaymentfee.com/api/v1/employees/199/ssn
- —All APIs on the platform are priced at $0.02 per request with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/employees/199/ssn