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 (ID 193) behind an x402 paywall. The endpoint accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x8335…2913) with a maximum cost of 20,000 base units, which equals $0.02 USD (USDC uses 6 decimals). No API keys or rate limits are required — access is gated purely by the x402 payment protocol.
The provider site (lowpaymentfee.com) hosts a broader catalog of pay-per-call APIs spanning data analytics, AI/ML inference, finance, and utility services, all priced at $0.02 per request. Documentation pages exist but appear to be stubs (returning only a "Connect wallet" prompt with no substantive content). There is no OpenAPI schema, no request/response examples, and no detailed documentation for this specific endpoint. The endpoint path suggests it returns personally identifiable information (an SSN), which raises significant regulatory and ethical concerns.
The x402 challenge was successfully captured (HTTP 402 with valid payment terms), confirming the endpoint is live. However, the lack of documentation, the absence of input/output schemas, and the sensitive nature of the data returned make this endpoint high-risk for any production use.
Capabilities
Use cases
- —Retrieving employee SSN for authorized payroll or HR integrations
- —Programmatic access to sensitive employee records behind a paywall
- —Agent-driven 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 the Base network
- —Low-volume, on-demand SSN lookups
Not for
- —Any use case where handling SSNs violates regulatory requirements (most contexts)
- —High-volume bulk PII retrieval
- —Production systems requiring documented schemas and SLAs
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/employees/193/ssn \
-H "X-PAYMENT: <x402_payment_token>" \
-H "Content-Type: application/json"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 the endpoint exposes highly sensitive PII (SSN) with no visible compliance or authorization framework. Documentation pages are empty stubs.
Warnings
- —This endpoint returns Social Security Numbers (PII). Handling SSNs is subject to strict regulatory requirements in most jurisdictions. Use with extreme caution.
- —No documentation, input schema, or response schema is available — the endpoint behavior is entirely opaque.
- —All documentation pages on the provider site return only a 'Connect wallet' stub with no substantive content.
- —The data source and legitimacy of the employee records are unknown. This could be synthetic/demo data or could raise serious legal issues if real.
- —No OpenAPI spec or ai-plugin manifest is provided.
Citations
- —Endpoint returns HTTP 402 with x402 challenge advertising USDC payment on Base networkhttps://lowpaymentfee.com/api/v1/employees/193/ssn
- —maxAmountRequired is 20000 base units of USDC (6 decimals) = $0.02https://lowpaymentfee.com/api/v1/employees/193/ssn
- —Provider site lists all APIs at $0.02 per request with no API keys, no rate limitshttps://lowpaymentfee.com
- —Documentation pages return only a 'Connect wallet' prompt with no contenthttps://lowpaymentfee.com/docs