x402basequality 0.30

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 137) behind an x402 paywall. It accepts POST requests and returns JSON. Payment is settled in USDC on the Base network using the x402 "exact" scheme.

The endpoint is part of a broader platform (lowpaymentfee.com) that offers various pay-per-call APIs across data analytics, AI/ML inference, finance, and utility categories — all priced at $0.02 per request. The platform advertises no API keys, no rate limits, and instant access; callers pay per request via the x402 protocol by attaching an X-PAYMENT header with a signed USDC payment.

The x402 challenge confirms the endpoint is live and requires a maximum of 20,000 base units of USDC (0.02 USDC, i.e., $0.02) per call. The payment is directed to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 on Base. No OpenAPI schema, request body documentation, or response schema was found in the crawl — the docs, pricing, and API pages all returned only a "Connect wallet" stub. The actual data returned by this endpoint and the input parameters it expects are unknown beyond what the x402 challenge describes.

Capabilities

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

Use cases

  • Retrieving employee SSN data for payroll or HR integrations
  • Programmatic identity verification workflows requiring SSN
  • Agent-driven data retrieval with per-call crypto micropayments

Fit

Best for

  • Developers needing on-demand SSN data without API key management
  • Automated agents that can settle x402 USDC payments on Base
  • Low-volume, pay-as-you-go access to sensitive employee records

Not for

  • Bulk SSN lookups requiring high throughput (no documented batch endpoint)
  • Users without a Base-network USDC wallet
  • Compliance-sensitive environments that prohibit transmitting SSNs over third-party APIs

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live (402 challenge captured) and pricing is clear ($0.02 USDC on Base), but there is no documentation for request parameters, response schema, or examples. The docs/pricing/API pages are all empty stubs. The endpoint exposes highly sensitive PII (SSN) with no visible compliance or authorization documentation, which is a significant red flag.

Warnings

  • Endpoint serves Social Security Numbers — highly regulated PII. No compliance, authorization, or data-source documentation is provided.
  • No request body schema or response schema documented anywhere in the crawl.
  • All documentation pages (docs, pricing, API, README) returned only a 'Connect wallet' stub with no useful content.
  • Unclear whether this returns real or synthetic/demo data; treat with extreme caution.
  • The specific employee ID (137) is hardcoded in the URL — unclear if other IDs are supported or how the dataset is sourced.

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-21 19:47:41Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-21
Last seen2026-04-25

Agent access

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