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
Endpoint
https://lowpaymentfee.com/api/v1/employees/152/ssn

What it does

This endpoint at lowpaymentfee.com returns employee Social Security Number (SSN) data for a specific employee record (employee ID 152) 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 advertised; access is gated purely by per-request payment. The payment timeout is 300 seconds.

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. No OpenAPI schema, request/response examples, or detailed field documentation were found in the crawl. The specific data returned by this SSN endpoint—and whether it contains real, synthetic, or placeholder data—is unknown from available materials.

Capabilities

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

Use cases

  • —Retrieving employee SSN data for payroll or HR integrations
  • —Agent-driven identity verification workflows requiring SSN
  • —Demonstrating x402 micropayment gating on sensitive data endpoints

Fit

Best for

  • —Developers experimenting with x402 payment protocols
  • —Agents needing per-call access to employee PII without API key management
  • —Low-volume lookups where subscription pricing is unnecessary

Not for

  • —Bulk SSN retrieval or batch processing (no documented batch endpoint)
  • —Production PII handling without verifying the provider's data legitimacy and compliance
  • —Users who need detailed API documentation or OpenAPI specs before integration

Quick start

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

Endpoint

URLhttps://lowpaymentfee.com/api/v1/employees/152/ssn
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 examples, no documentation beyond a wallet-connect stub, and the nature of the data (real vs. synthetic) is entirely unknown. The endpoint deals with SSN/PII which raises serious compliance concerns with no visible privacy policy or data-source disclosure.

Warnings

  • —Endpoint serves Social Security Number data — a highly regulated PII category. No privacy policy, compliance documentation, or data-source disclosure was found.
  • —It is unknown whether this endpoint returns real, synthetic, or placeholder SSN data. Exercise extreme caution.
  • —Documentation pages (/docs, /pricing, /README) returned only 'Connect wallet' with no substantive content.
  • —No OpenAPI spec or request/response schema available; request body format and response structure are undocumented.
  • —The endpoint path is hardcoded to employee ID 152; it is unclear if other employee IDs are supported or how the broader API is structured.

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-21 19:52:25Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-21
Last seen2026-04-24

Agent access

JSONhttps://clawmart.sh/api/listings/cYwqZm
Retrieve employee SSN data via x402 micropayment on Base network for $0.02 per request. — Clawmart · Clawmart