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 13 in this case). It is part of a broader suite of pay-per-request APIs offered by the same provider, all settling payments in USDC on the Base L2 network.
The endpoint accepts POST requests and requires an X-PAYMENT header conforming to the x402 protocol (version 1, "exact" scheme). The maximum amount required is 20,000 base units of USDC (0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base), which equals $0.02 USD (USDC uses 6 decimals). Payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout window. The response MIME type is application/json.
The provider's landing page advertises a uniform $0.02/request pricing model across all endpoints with no API keys, no rate limits, and instant access. However, the documentation, pricing, and README pages all returned only a "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no request/response examples, and no documentation describing the shape of the returned SSN data. The nature of this endpoint—returning personally identifiable information (SSN)—raises significant regulatory and ethical concerns. It is unclear whether this is a demo/test dataset or real PII.
Capabilities
Use cases
- —Retrieving employee SSN records via automated micropayment
- —Integrating pay-per-request PII lookups into agent workflows
- —Testing x402 protocol payment flows against a live endpoint
Fit
Best for
- —Developers testing x402 payment protocol integrations
- —Agents needing on-demand employee data retrieval with crypto settlement
- —Exploring pay-per-request API patterns on Base network
Not for
- —Production use involving real PII without verifying regulatory compliance
- —Users who need detailed API documentation or OpenAPI schemas
- —Anyone without a Base-network USDC wallet
Quick start
# 1. Obtain an x402 payment token for 20000 base-unit USDC on Base
# 2. POST with X-PAYMENT header
curl -X POST https://lowpaymentfee.com/api/v1/employees/13/ssn \
-H "X-PAYMENT: <your-x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live (402 challenge captured) and pricing is clear ($0.02 USDC on Base), but there is zero documentation on request/response schemas, no OpenAPI spec, no examples, and the docs pages are empty. The endpoint serves highly sensitive PII (SSN) with no visible compliance or data-source information, which is a major red flag.
Warnings
- —Endpoint returns employee SSN data — highly sensitive PII. Regulatory compliance (e.g., FCRA, GDPR, state privacy laws) is unverified.
- —No documentation available: /docs, /pricing, /README, and /api all return only a 'Connect wallet' prompt with no content.
- —No OpenAPI schema or request/response examples provided; response shape is unknown.
- —It is unclear whether this is real PII or synthetic/demo data.
- —No robots.txt or agents.txt found on the origin.
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base-unit USDC on Base networkhttps://lowpaymentfee.com/api/v1/employees/13/ssn
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/employees/13/ssn
- —Provider advertises $0.02/request uniform pricing with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —Documentation pages (/docs, /pricing, /README, /api) contain only 'Connect wallet' with no substantive contenthttps://lowpaymentfee.com/docs