x402basequality 0.35

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 28) 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 given USDC's 6 decimals. This is consistent with the provider's site-wide pricing of $0.02 per request. No API keys or rate limits are required — access is gated purely by the x402 payment header. The payment timeout is 300 seconds.

The provider (lowpaymentfee.com) hosts a broad catalog of x402-gated APIs spanning data analytics, AI/ML inference, finance, and utility services, all at the same $0.02/request price point. Documentation pages exist but appear to require a wallet connection to view, so detailed request/response schemas are not available from the crawl. The specific nature of the data returned by this SSN endpoint — whether it is synthetic/demo data or real PII — is not documented in the crawl material.

Capabilities

x402-paymentusdc-baseemployee-datassn-lookupjson-responseper-request-pricing

Use cases

  • Retrieving employee SSN data on a per-request payment basis without API key management
  • Integrating SSN lookups into agent workflows that support x402 payment flows
  • Demonstrating x402 micropayment protocol usage on Base network

Fit

Best for

  • Agents or applications that need on-demand employee PII retrieval via crypto micropayments
  • Developers exploring x402 protocol integrations on Base
  • Workflows requiring keyless, pay-per-use API access

Not for

  • Use cases requiring bulk employee data retrieval (single-record endpoint)
  • Applications that cannot settle payments in USDC on Base network
  • Scenarios where handling real SSN/PII data would violate compliance requirements

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.35/ 1.00

The endpoint is live and returns a valid x402 challenge with clear pricing. However, there is no documentation of request parameters, response schema, or the nature of the data (real vs. synthetic). The docs, API, pricing, and README pages all resolve to a wallet-connect prompt with no useful content. The endpoint path suggests sensitive PII, which raises significant compliance concerns.

Warnings

  • Endpoint path suggests it returns Social Security Numbers — this is highly sensitive PII. Verify whether data is real or synthetic/demo before use.
  • No request or response schema is documented; the crawl yielded no usable documentation beyond the landing page.
  • Handling real SSNs may implicate federal and state privacy regulations (e.g., GLBA, state SSN protection laws). Assess compliance before integrating.
  • The endpoint is scoped to a single employee ID (28); it is unclear if other employee IDs are supported or if this is a demo.

Citations

Provenance

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

Agent access