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 180) 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), which equals $0.02 USD (USDC uses 6 decimals). 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.

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 per-call price point. Documentation beyond the landing page is essentially empty (pages return only a "Connect wallet" prompt), so the exact request body schema and response format for this SSN endpoint are unknown. The endpoint is live and returning a valid 402 challenge.

Capabilities

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

Use cases

  • Retrieving SSN data for a specific employee record via programmatic API call
  • Integrating employee identity verification into automated workflows
  • Demonstrating x402 micropayment-gated access to sensitive data

Fit

Best for

  • Developers needing on-demand access to employee PII without API key management
  • Agents that can settle x402 USDC payments on Base for per-call data access
  • Prototyping pay-per-call access patterns for sensitive data endpoints

Not for

  • Bulk retrieval of employee records (only a single employee ID 180 is exposed at this URL)
  • Use cases requiring detailed API documentation or request/response schemas
  • Applications where handling PII (SSNs) raises regulatory or compliance concerns you haven't addressed

Quick start

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

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, no request/response schema, no examples, and the endpoint exposes PII (SSN) with no visible compliance or authorization framework. The docs pages are all blank beyond a wallet connect prompt.

Warnings

  • Endpoint exposes Social Security Number (SSN) data — a highly regulated category of PII. Ensure compliance with applicable laws (e.g., FCRA, state privacy laws) before use.
  • No request body schema or response schema is documented; callers must guess the expected input format.
  • Documentation pages (/docs, /api, /pricing, /README) are effectively empty, returning only 'Connect wallet'.
  • Only a single employee ID (180) is referenced in this endpoint URL; unclear if other IDs are supported or if this is a demo/test record.
  • The broader platform lists many API categories (AI, finance, analytics) all at $0.02 — unclear whether these are real production services or placeholders.

Citations

Provenance

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

Agent access