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 98). It is part of a broader suite of x402-protocol APIs offered by the provider, all priced at $0.02 per request and settled in USDC on the Base network. The endpoint uses the x402 payment protocol: callers receive a 402 challenge and must include an X-PAYMENT header with a valid payment proof to access the resource.
The x402 challenge specifies an "exact" payment scheme with a maxAmountRequired of 20,000 base units of USDC (0x8335… on Base), which equals $0.02 given USDC's 6 decimals. Payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout. The response MIME type is application/json. The endpoint accepts POST requests and is marked as discoverable.
The provider's landing page advertises a wide catalog of APIs spanning data/analytics, AI/ML, finance/Web3, and infrastructure utilities, all at the same $0.02 per-request price point with no API keys, no rate limits, and instant access. However, documentation pages (docs, pricing, README) returned only a "Connect wallet" prompt with no substantive content, so there is no schema documentation for request bodies or response shapes beyond what the x402 challenge provides.
Capabilities
Use cases
- —Programmatic retrieval of employee SSN for payroll or HR integrations
- —Agent-driven identity verification workflows requiring SSN data
- —Automated compliance checks that need SSN on demand
Fit
Best for
- —Agents or services that need on-demand SSN data without API key management
- —x402-compatible clients settling micropayments in USDC on Base
- —Low-volume, pay-per-use access to sensitive employee records
Not for
- —Bulk data exports of many employee records (single-employee endpoint)
- —Users who cannot settle USDC payments on the Base network
- —Use cases where handling SSN data would violate privacy regulations
Quick start
# 1. Probe the endpoint to get the 402 challenge
curl -X POST https://lowpaymentfee.com/api/v1/employees/98/ssn
# 2. Construct an X-PAYMENT header per x402 spec (exact scheme, USDC on Base)
# 3. Re-send with payment proof:
curl -X POST https://lowpaymentfee.com/api/v1/employees/98/ssn \
-H "X-PAYMENT: <payment-proof>"Endpoint
Quality
The endpoint is live (402 challenge captured) and pricing is clear ($0.02 USDC on Base). However, there is no documentation for request body schema or response shape, no OpenAPI spec, and the docs/pricing/README pages are empty. The endpoint deals with highly sensitive PII (SSN) with no visible access controls beyond payment, which is a significant concern.
Warnings
- —Endpoint returns sensitive PII (Social Security Numbers) — ensure compliance with applicable privacy and data protection regulations before use.
- —No request body schema or response schema documented; callers must discover the format experimentally.
- —All documentation pages (docs, pricing, README) returned only 'Connect wallet' with no content.
- —The endpoint is for a single hardcoded employee ID (98); unclear if other IDs are supported or how to discover them.
- —No information on data provenance or whether this is real or synthetic/demo data.
Citations
- —x402 challenge returns maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/employees/98/ssn
- —USDC asset address is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/employees/98/ssn
- —All APIs priced at $0.02 per request with no API keys, no rate limits, instant accesshttps://lowpaymentfee.com
- —Payment timeout is 300 seconds, payTo address is 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3https://lowpaymentfee.com/api/v1/employees/98/ssn