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 153) behind an x402 paywall. The endpoint accepts POST requests and is settled in USDC on the Base network. The x402 challenge advertises a maxAmountRequired of 20,000 base units of USDC (6 decimals), which equals $0.02 per request.

The provider site lowpaymentfee.com hosts a broad catalog of pay-per-call APIs spanning data analytics, AI/ML inference, finance, and utility services — all priced at $0.02 per request with no API keys, no rate limits, and no commitments. This particular endpoint falls outside those listed categories and appears to serve sensitive personally identifiable information (PII). The endpoint is live and returns a proper 402 challenge, but documentation beyond the landing page is essentially empty (all subpages just show "Connect wallet").

Because this endpoint purports to serve Social Security Numbers — highly regulated PII in the United States — consumers should exercise extreme caution. There is no documentation explaining the data source, authorization model, compliance posture, or legal basis for distributing SSNs. The endpoint may be a demonstration, a honeypot, or a test fixture; there is no way to confirm from available materials.

Capabilities

x402-paymentusdc-basepii-lookupemployee-dataper-request-micropaymentpost-method

Use cases

  • Retrieving employee SSN for identity verification workflows (if legally authorized)
  • Demonstrating x402 micropayment protocol integration
  • Testing pay-per-call API patterns on Base network

Fit

Best for

  • Developers testing x402 payment flows on Base
  • Scenarios where per-call PII access is legally permissible and needed

Not for

  • Any use case lacking explicit legal authorization to handle SSNs
  • Production identity verification without confirming data provenance and compliance
  • Bulk PII harvesting or unauthorized background checks

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/employees/153/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 on request/response schema, no OpenAPI spec, and the docs/pricing/README pages are all blank. The endpoint serves highly sensitive PII (SSNs) with no stated compliance or legal framework, which is a major red flag.

Warnings

  • Endpoint claims to serve Social Security Numbers — highly regulated PII under US law (FCRA, GLBA, state privacy laws). No compliance documentation found.
  • No request or response schema available; impossible to verify what data is actually returned.
  • All documentation pages (docs, api, pricing, README) are empty beyond a 'Connect wallet' prompt.
  • Data provenance is unknown — no indication of whether this is real, synthetic, or test data.
  • This endpoint targets a hardcoded employee ID (153); unclear if other IDs are supported or if this is a demo fixture.

Citations

Provenance

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

Agent access