x402basequality 0.25

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

What it does

This endpoint at lowpaymentfee.com returns employee Social Security Number (SSN) data for a specific employee record (ID 86) 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 site also offers endpoints in categories like data analytics, AI/ML inference, finance, and infrastructure utilities — all at the same price point.

Documentation is extremely sparse. The /docs, /pricing, /api, and /README pages all returned only a "Connect wallet" prompt with no substantive content. There is no OpenAPI spec, no request/response schema documentation, and no explanation of what data is actually returned or what input the POST body expects. The endpoint path suggests it returns a Social Security Number for employee ID 86, which raises significant data sensitivity and regulatory concerns.

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
  • —Programmatic access to sensitive employee records with per-call payment

Fit

Best for

  • —Developers needing pay-per-call access to employee data without API key management
  • —Agents that can settle x402 payments in USDC on Base
  • —Use cases where per-request billing is preferred over subscriptions

Not for

  • —Users needing bulk employee data exports (no batch endpoint documented)
  • —Applications requiring detailed API documentation or OpenAPI specs before integration
  • —Scenarios where handling SSN data would violate compliance requirements (HIPAA, state privacy laws)

Quick start

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

Endpoint

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

Quality

0.25/ 1.00

The endpoint is live (402 challenge captured) and pricing is clear ($0.02 USDC on Base), but there is zero documentation on request format, response schema, or what data is actually returned. The SSN-related path raises serious regulatory red flags with no compliance information provided. No OpenAPI spec, no examples, no docs beyond a wallet-connect prompt.

Warnings

  • —Endpoint appears to serve Social Security Number data — handling SSN is subject to strict regulations (e.g., state privacy laws, IRS Publication 1075, GLBA). No compliance or data-handling documentation is provided.
  • —No request body schema or response schema documented anywhere. It is unknown what POST body is expected or what the response contains.
  • —All documentation pages (/docs, /pricing, /api, /README) returned only 'Connect wallet' with no useful content.
  • —The endpoint is hardcoded to employee ID 86 — it is unclear whether other employee IDs are supported or if this is a demo/test endpoint.
  • —No OpenAPI specification or ai-plugin manifest available.

Citations

Provenance

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

Agent access

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