x402basequality 0.25

Retrieve employee SSN data via x402 micropayment on Base network for $0.02 per request.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com returns employee Social Security Number (SSN) data for a given employee ID (in this case, employee 90). It is part of a broader suite of pay-per-request APIs offered by lowpaymentfee.com, all gated behind the x402 payment protocol. Payment is settled in USDC on the Base network at $0.02 per request (maxAmountRequired of 20,000 base units with 6 decimals = $0.02).

The endpoint accepts POST requests and returns JSON. No API keys or account registration are required — access is granted by including a valid X-PAYMENT header with a USDC micropayment. The x402 challenge confirms the endpoint is live and operational. The broader lowpaymentfee.com platform also offers endpoints for analytics, AI/ML inference, finance data, and utility services, all at the same $0.02/request price point.

Documentation is extremely sparse. The docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI schema, no request/response examples, and no description of what fields the SSN endpoint returns or what input parameters it expects beyond the employee ID in the URL path. The nature of this data (SSN retrieval) raises significant regulatory and privacy concerns.

Capabilities

employee-ssn-lookupx402-paymentusdc-micropaymentbase-networkpay-per-requestjson-response

Use cases

  • Retrieving employee SSN for payroll or HR verification workflows
  • Programmatic access to sensitive employee identifiers
  • Automated compliance checks requiring SSN data

Fit

Best for

  • Agents needing on-demand SSN lookups without API key registration
  • Pay-per-use access to employee PII data
  • x402-native workflows on Base network

Not for

  • Bulk data exports of employee records (single-record endpoint)
  • Users who need detailed API documentation or schema guarantees
  • Use cases where handling PII without clear compliance documentation is unacceptable

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/employees/90/ssn \
  -H "X-PAYMENT: <x402-payment-token>" \
  -H "Content-Type: application/json"

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.25/ 1.00

The x402 challenge is live and pricing is clear ($0.02/request in USDC on Base). However, there is zero documentation on request parameters, response schema, or data provenance. The endpoint deals with highly sensitive PII (SSNs) with no visible compliance, privacy, or legal documentation. No OpenAPI spec, no examples, and all doc pages are empty.

Warnings

  • Endpoint returns Social Security Numbers — highly regulated PII under US law (e.g., FCRA, state privacy laws). No compliance documentation is visible.
  • No API documentation, OpenAPI schema, or response examples are available — all doc pages render only 'Connect wallet'.
  • Data provenance and legitimacy of the SSN data is completely unknown. Use with extreme caution.
  • This may be a demo or test endpoint; the employee ID '90' is hardcoded in the URL path.

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-21 20:53:20Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-21
Last seen2026-04-24

Agent access