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

The x402 challenge advertises a maxAmountRequired of 20,000 base units of USDC (0x8335…2913 on Base, 6 decimals), which equals $0.02 per request. The provider's landing page confirms a flat $0.02/request pricing model across all their API endpoints, with no API keys, no rate limits, and instant access. The endpoint was live at probe time, returning a valid 402 challenge.

This endpoint is part of a broader platform (lowpaymentfee.com) that offers data & analytics, AI/ML inference, finance/Web3, and infrastructure utility APIs — all at the same $0.02/request price point. Documentation beyond the landing page is essentially empty (pages return only "Connect wallet"), so the exact request body schema and response format for this SSN endpoint are unknown. The nature of the data returned (employee SSN) raises significant regulatory and privacy concerns — callers should verify the legitimacy and compliance of this data source before use.

Capabilities

x402-paymentusdc-baseemployee-datassn-lookupper-request-micropaymentjson-response

Use cases

  • Retrieving employee SSN for payroll or HR verification workflows
  • Programmatic access to sensitive employee identifiers behind a paywall
  • Agent-driven data retrieval with per-call USDC micropayments

Fit

Best for

  • Developers needing on-demand employee SSN data via crypto micropayments
  • Automated agents that can settle x402 payments on Base
  • Use cases where API-key-free, pay-per-call access is preferred

Not for

  • Users who need bulk employee data exports (single-record endpoint)
  • Applications requiring documented request/response schemas before integration
  • Scenarios where regulatory compliance around PII handling is uncertain

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 402 challenge, but there is no documentation on request body format, response schema, or what data is actually returned. The docs, pricing, and README pages are all empty. The endpoint deals with highly sensitive PII (SSN) with no visible compliance or legitimacy information.

Warnings

  • Endpoint returns employee SSN data — highly sensitive PII. Verify regulatory compliance (e.g., FCRA, state privacy laws) before use.
  • No documentation available: request body schema and response format are completely unknown.
  • Only a single hardcoded employee ID (35) is visible in the endpoint path; unclear if other IDs are supported.
  • Provider docs pages are empty ('Connect wallet' only), suggesting the platform may be incomplete or a demo.
  • Legitimacy of the data source is unverified — this could be synthetic/demo data or raise legal concerns if real.

Citations

Provenance

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

Agent access

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