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 156) behind an x402 paywall. It accepts POST requests and is settled in USDC on the Base network. The x402 challenge advertises a maxAmountRequired of 20,000 base units of USDC (6 decimals), which equals $0.02 per request.

The provider lowpaymentfee.com hosts a broad catalog of x402-gated APIs spanning data analytics, AI/ML inference, finance, crypto, and utility endpoints, all priced at $0.02 per call. The site advertises no API keys, no rate limits, and instant access. However, this specific endpoint — exposing what appears to be personally identifiable information (an employee's SSN) — raises significant concerns about data sensitivity, legality, and ethical use. No documentation, input schema, or response schema is provided beyond the x402 challenge metadata.

The endpoint is live and returns a valid x402 challenge (HTTP 402 with version 1 accepts block). The output MIME type is application/json. No OpenAPI spec, ai-plugin manifest, or detailed docs were found in the crawl. The docs, API, pricing, and README pages all returned only a "Connect wallet" prompt with no substantive content.

Capabilities

x402-paymentusdc-baseemployee-datassn-lookupjson-responsepost-method

Use cases

  • Retrieving an employee's SSN for payroll or HR verification workflows
  • Programmatic access to sensitive employee records behind a micropayment wall
  • Agent-driven identity verification requiring SSN data

Fit

Best for

  • Developers needing pay-per-call access to employee PII without API key management
  • Automated HR or payroll systems that need SSN lookups
  • x402-compatible agents on the Base network

Not for

  • Anyone without a legitimate, lawful need for SSN data — exposing SSNs raises serious legal and ethical concerns
  • Use cases requiring bulk data export or batch processing (no documented batch endpoint)
  • Users who need detailed documentation or guaranteed SLAs

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/employees/156/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 challenge, but there is no OpenAPI spec, no input/output schema beyond MIME type, no documentation, and no example responses. The endpoint exposes what appears to be highly sensitive PII (SSN), which is a major red flag. The crawl yielded almost no useful documentation.

Warnings

  • This endpoint claims to return Social Security Numbers (SSNs), which are highly sensitive PII. Accessing, storing, or transmitting SSNs is subject to strict legal regulations (e.g., FCRA, state privacy laws). Use with extreme caution and only for lawful purposes.
  • No input schema or response schema is documented — the actual data returned is unknown.
  • No OpenAPI spec or detailed API documentation was found; docs pages returned only a wallet-connect prompt.
  • The endpoint is hardcoded to employee ID 156; it is unclear whether other employee IDs are supported or what the data source is.
  • Legitimacy of the underlying data is unverified — this could be synthetic/demo data or could pose real privacy risks.

Citations

Provenance

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

Agent access