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/70/ssn

What it does

This endpoint at lowpaymentfee.com returns employee Social Security Number (SSN) data for a specific employee record (employee ID 70) 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, 6 decimals), which equals $0.02 per request. The provider's landing page confirms a flat $0.02/request pricing model across all their API endpoints, with no API keys, no rate limits, and instant access. The endpoint is live and returning a valid 402 challenge.

This endpoint is part of a broader platform (lowpaymentfee.com) that offers data & analytics, AI/ML inference, finance/Web3, and infrastructure utility APIs — all at the same $0.02 per-call price point. Documentation beyond the landing page is essentially empty (all sub-pages just show "Connect wallet"), so there is no schema documentation for request body parameters or response format. The nature of the data returned (employee SSN) raises significant regulatory and privacy concerns — SSNs are personally identifiable information (PII) subject to strict handling requirements in most jurisdictions.

Capabilities

x402-paymentusdc-baseemployee-datassn-lookupjson-responseper-call-micropayment

Use cases

  • —Retrieving employee SSN for payroll or HR integrations
  • —Programmatic identity verification workflows
  • —Automated compliance checks requiring SSN data

Fit

Best for

  • —Developers needing pay-per-call access to employee PII without API key management
  • —Agent-based workflows that can settle USDC payments on Base
  • —Low-volume lookups where subscription pricing is unnecessary

Not for

  • —Production systems requiring documented request/response schemas
  • —Use cases where handling SSN data would violate privacy regulations
  • —High-volume bulk data retrieval (no documented batch endpoint)

Quick start

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

Endpoint

URLhttps://lowpaymentfee.com/api/v1/employees/70/ssn
Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 402 challenge, but documentation is essentially nonexistent — all doc/pricing/API pages show only 'Connect wallet'. There is no request or response schema, no examples, and the endpoint deals with highly sensitive PII (SSNs) with no documented compliance or authorization framework. The hardcoded employee ID (70) in the URL path raises questions about the endpoint's actual utility.

Warnings

  • —Endpoint returns employee SSN data — this is highly sensitive PII subject to strict regulatory requirements (e.g., HIPAA, state privacy laws, GDPR-adjacent rules). Ensure compliance before use.
  • —No documentation exists for request body format or response schema — all doc pages return only 'Connect wallet'.
  • —The endpoint path is hardcoded to employee ID 70; it is unclear whether other employee IDs are supported or what authorization controls exist.
  • —The legitimacy and provenance of the employee data served by this endpoint is unknown. Use extreme caution.

Citations

Provenance

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

Agent access

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