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 (ID 95) behind an x402 paywall. The endpoint accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) with a maximum cost of $0.02 per request (20,000 base units at 6 decimals).

The provider site lowpaymentfee.com hosts a broad catalog of x402-gated APIs spanning data analytics, AI/ML inference, finance, and utility services, all priced at $0.02 per call. No API keys or rate limits are advertised; access is granted purely via the x402 payment header. The site root returns HTTP 200 and the x402 challenge is live.

However, this specific endpoint purports to serve personally identifiable information (an employee's SSN). There is no documentation explaining the data source, whether this is synthetic/demo data, or what legal framework governs its use. The docs, pricing, and API pages on the site are essentially empty (showing only a "Connect wallet" prompt). No OpenAPI schema, request/response examples, or data provenance information is available. Users should exercise extreme caution given the sensitive nature of SSN data and the complete lack of documentation about its origin or legitimacy.

Capabilities

x402-paymentusdc-base-networkemployee-datassn-lookupjson-responseno-api-keyper-request-billing

Use cases

  • Retrieving employee SSN data for payroll or identity verification workflows (if data source is legitimate and compliant)
  • Demonstrating x402 payment protocol integration on Base network
  • Testing micropayment-gated API access patterns

Fit

Best for

  • Developers exploring x402 protocol mechanics
  • Testing micropayment flows on Base with USDC
  • Prototyping pay-per-call data access patterns

Not for

  • Production PII retrieval without verified data provenance and legal compliance
  • Any use case requiring documented data sources and audit trails
  • Regulated industries needing SOC2/HIPAA-compliant data handling

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/employees/95/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 USDC on Base), but there is zero documentation, no OpenAPI schema, no request/response examples, and the endpoint serves highly sensitive PII (SSN) with no explanation of data provenance or legal compliance. The docs/pricing/API pages are empty stubs.

Warnings

  • Endpoint serves personally identifiable information (SSN) with no documentation about data source, legitimacy, or legal compliance
  • No OpenAPI schema, request body specification, or response examples available
  • Docs, pricing, and API pages are empty — only show 'Connect wallet'
  • Potential regulatory risk: SSN data may be subject to privacy laws (e.g., CCPA, state SSN protection statutes)
  • Data provenance is completely unknown — could be synthetic, leaked, or fabricated

Citations

Provenance

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

Agent access