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 Social Security Number (SSN) data for a specific employee record (employee ID 75). It is part of a broader platform offering various pay-per-request APIs spanning data analytics, AI/ML inference, finance, and utility services — all gated behind x402 payment challenges on the Base network using USDC.
The endpoint accepts POST requests and returns JSON. Payment is settled on-chain via USDC on Base (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) using the x402 "exact" scheme. The maximum amount required per call is 20,000 base units of USDC (6 decimals), which equals $0.02 USD. The payment recipient address is 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3, with a maximum timeout of 300 seconds.
No OpenAPI schema, detailed documentation, or example responses were found during the crawl — the docs, pricing, and API pages all returned only a "Connect wallet" prompt. The endpoint is confirmed live (returns a valid 402 challenge). However, the nature of the data returned (employee SSN) raises significant regulatory and privacy concerns. There is no indication of what input parameters are expected in the POST body beyond the employee ID embedded in the URL path.
Capabilities
Use cases
- —Retrieving employee SSN for payroll or HR verification workflows
- —Programmatic access to sensitive employee records with per-request payment
- —Agent-driven identity verification requiring SSN data
Fit
Best for
- —Automated HR or payroll systems needing SSN lookups
- —x402-compatible agents with USDC on Base
- —Pay-per-use access to employee records without API key management
Not for
- —Bulk data export of employee records (single-record endpoint with hardcoded ID)
- —Users without USDC on Base network
- —Use cases where handling PII/SSN data would violate regulatory requirements (GDPR, CCPA, etc.)
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/employees/75/ssn \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but there is no documentation, no OpenAPI schema, no example request/response, and the endpoint path is hardcoded to a single employee ID. The data type (SSN/PII) raises serious regulatory red flags with no visible compliance documentation.
Warnings
- —Endpoint returns employee SSN (PII/sensitive data) — ensure compliance with applicable privacy regulations (CCPA, GDPR, SOC 2, etc.) before use.
- —No documentation, OpenAPI schema, or example responses available — actual response format is unknown.
- —Endpoint path is hardcoded to employee ID 75; it is unclear whether other employee IDs are supported or how to parameterize requests.
- —The broader platform (lowpaymentfee.com) docs/pricing/API pages returned only 'Connect wallet' with no substantive content.
- —No information on data provenance, authorization model, or whether this is real or synthetic data.
Citations
- —The endpoint returns a 402 challenge with x402Version 1, accepting USDC on Base with maxAmountRequired of 20000 base units ($0.02).https://lowpaymentfee.com/api/v1/employees/75/ssn
- —The platform advertises $0.02 per request pricing with no API keys, no rate limits, and instant access on Base network.https://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913.https://lowpaymentfee.com/api/v1/employees/75/ssn