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 (ID 24) 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. The provider advertises no API keys, no rate limits, and instant access — payment is handled entirely through the x402 protocol's X-PAYMENT header.

The provider (lowpaymentfee.com) hosts a broad catalog of x402-gated endpoints spanning data analytics, AI/ML inference, finance, and utility services, all at the same $0.02 price point. Documentation pages exist but appear to require a wallet connection and contain no substantive content. There is no OpenAPI schema, no request/response examples, and no detail on what fields the SSN endpoint actually returns. The endpoint path suggests it returns personally identifiable information (PII), specifically a Social Security Number, which raises significant regulatory and ethical concerns.

Capabilities

x402-paymentusdc-baseemployee-datassn-lookuppii-retrievaljson-responsepost-method

Use cases

  • Retrieving employee SSN for payroll or HR verification workflows
  • Programmatic access to sensitive employee identifiers behind a paywall
  • Agent-driven data retrieval where x402 micropayments replace API keys

Fit

Best for

  • Developers experimenting with x402 payment protocol integrations
  • Automated workflows needing on-demand employee PII access
  • Testing x402 micropayment flows on Base network

Not for

  • Production systems requiring compliance with PII regulations (GDPR, CCPA, etc.)
  • Use cases where SSN data provenance and legitimacy must be verified
  • Applications needing bulk employee data retrieval (single-employee endpoint)

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/employees/24/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 (402 challenge captured) and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI schema, no request/response documentation, no examples, and the docs pages are empty. The endpoint purports to serve SSN data, which is highly sensitive PII with no indication of data provenance, legitimacy, or compliance framework.

Warnings

  • Endpoint claims to return Social Security Number (SSN) data — highly sensitive PII. No information on data provenance, authorization, or regulatory compliance.
  • No documentation, OpenAPI schema, or response examples available — impossible to verify what the endpoint actually returns.
  • All documentation pages (docs, api, pricing, README) render only a 'Connect wallet' prompt with no substantive content.
  • Serving SSN data via a public paywall with no authentication beyond payment raises serious legal and ethical red flags (potential violations of FCRA, GLBA, state privacy laws).
  • This may be a demo or test endpoint rather than a real PII data source — exercise extreme caution.

Citations

Provenance

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

Agent access