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 specific employee record (employee ID 85). It is part of a broader suite of pay-per-request APIs offered by lowpaymentfee.com, all gated behind the x402 payment protocol. The endpoint accepts POST requests and returns JSON.

Payment is settled on the Base network using USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913). The x402 challenge advertises a maxAmountRequired of 20000 base units, which at 6 decimals for USDC equals $0.02 per request. The provider's landing page confirms a flat $0.02/request pricing model across all their endpoints, with no API keys, no rate limits, and no minimum commitments required.

The endpoint is live and returning a valid x402 402 challenge. However, the nature of the data returned — employee SSN — raises significant regulatory and ethical concerns. SSNs are highly sensitive personally identifiable information (PII) subject to strict legal protections in the United States. There is no documentation available beyond the landing page, and the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no substantive content. The actual data source, legitimacy, and compliance posture of this endpoint are entirely unknown.

Capabilities

x402-paymentusdc-base-networkemployee-datassn-lookuppay-per-requestjson-response

Use cases

  • Retrieving employee SSN for payroll or HR verification workflows
  • Programmatic access to sensitive employee identifiers
  • Agent-driven identity verification pipelines

Fit

Best for

  • Developers needing pay-per-call access to employee PII without API key management
  • Automated workflows requiring SSN data with crypto-native payment

Not for

  • Anyone without a clear legal basis to access SSNs — unauthorized access to SSNs may violate federal and state law
  • Production use without verifying the data source's legitimacy and compliance with privacy regulations
  • Use cases requiring documented data provenance or audit trails — no documentation is provided

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/employees/85/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 endpoint is live and returns a valid x402 challenge, but there is zero documentation, no request/response schema, no explanation of the data source, and the endpoint serves highly sensitive PII (SSNs) with no visible compliance or legal framework. The docs pages are all empty 'Connect wallet' stubs.

Warnings

  • CRITICAL: This endpoint claims to serve Social Security Numbers, which are highly regulated PII. Accessing, distributing, or purchasing SSNs without proper legal authorization may violate US federal law (e.g., the Privacy Act, FCRA) and state laws.
  • No documentation is available — all doc pages render only 'Connect wallet' with no content.
  • Data provenance is completely unknown. There is no indication whether the returned data is real, synthetic, or fabricated.
  • No request or response schema is documented; the actual payload structure must be discovered empirically.
  • The endpoint is hardcoded to employee ID 85 — it is unclear if other employee IDs are supported or what the broader data set is.

Citations

Provenance

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

Agent access