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 74). It is part of a broader platform offering various pay-per-request APIs spanning data analytics, AI/ML inference, finance, and utility services, all gated behind the x402 payment protocol on the Base network using USDC.

The endpoint accepts POST requests and returns JSON. Payment is handled via the x402 protocol: callers must include an X-PAYMENT header with a valid payment proof. The maximum amount required is 20,000 base units of USDC (0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base), which equals $0.02 USD (USDC uses 6 decimals). The payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a timeout of 300 seconds.

Important caveat: This endpoint purports to return SSN data, which is highly sensitive personally identifiable information (PII). The legitimacy, legality, and data source of this endpoint are entirely unclear from the available documentation. The provider's landing page lists many generic API categories but provides no documentation about data provenance, compliance, or authorization. Prospective users should exercise extreme caution and verify legal compliance before interacting with this endpoint.

Capabilities

x402-paymentusdc-baseemployee-datassn-lookuppay-per-requestjson-responsepost-method

Use cases

  • Retrieving employee SSN data for authorized payroll or HR integrations
  • Demonstrating x402 micropayment protocol usage on Base network
  • Pay-per-request access to sensitive employee records

Fit

Best for

  • Developers exploring x402 payment protocol integrations
  • Authorized HR/payroll systems needing programmatic SSN access
  • Testing micropayment-gated API patterns on Base

Not for

  • Unauthorized access to personal information — legal compliance is the caller's responsibility
  • Production PII workflows without verified data provenance and compliance guarantees
  • Users who need free or subscription-based API access

Quick start

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

Example

Request

{
  "url": "https://lowpaymentfee.com/api/v1/employees/74/ssn",
  "method": "POST",
  "headers": {
    "X-PAYMENT": "<x402-payment-proof>",
    "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 documentation of request/response format, no example responses, and the endpoint claims to serve highly sensitive PII (SSN) with no information about data provenance, authorization, or legal compliance. The broader site's docs/pricing/API pages are empty ('Connect wallet' only).

Warnings

  • Endpoint claims to return Social Security Number data — highly sensitive PII. Legal compliance (e.g., FCRA, state privacy laws) is entirely unverified.
  • No documentation exists for request body format or response schema.
  • Data provenance is unknown — it is unclear whether this returns real, synthetic, or fabricated data.
  • The provider site has no meaningful documentation beyond the landing page listing.
  • The employee ID (74) is hardcoded in the URL; it is unclear if other IDs are supported or what the data source is.

Citations

Provenance

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

Agent access