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

What it does

This endpoint at lowpaymentfee.com returns employee Social Security Number (SSN) data for a specific employee record (ID 96) behind an x402 paywall. The endpoint 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, and utility services, all priced at $0.02 per request with no API keys, no rate limits, and no minimum commitments. However, this specific endpoint — /api/v1/employees/96/ssn — is not listed on the provider's public landing page among the advertised API categories. It appears to serve sensitive personally identifiable information (an employee's SSN), which raises significant regulatory and ethical concerns.

Documentation is extremely sparse. The docs, API, pricing, and README pages all returned only a "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no request/response examples, and no description of what input the POST body expects or what the response payload looks like beyond the stated mimeType of application/json.

Capabilities

x402-paymentusdc-baseemployee-datassn-lookupmicropaymentpost-endpoint

Use cases

  • Retrieving SSN for employee record 96 via automated payment
  • Integrating employee PII lookups into payroll or HR workflows
  • Agent-driven identity verification requiring SSN data

Fit

Best for

  • Programmatic access to employee SSN data without API key management
  • x402-native agents that can settle USDC on Base
  • Low-cost per-request PII retrieval

Not for

  • Bulk employee data exports (endpoint is scoped to a single employee ID)
  • Use cases where handling SSN data would violate privacy regulations (GDPR, CCPA, etc.)
  • Users who need documented request/response schemas before integration

Quick start

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

Endpoint

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/response schema, no OpenAPI spec, no examples, and the endpoint is not listed on the provider's own landing page. The endpoint serves highly sensitive PII (SSN) with no visible compliance or authorization framework documented.

Warnings

  • Endpoint serves personally identifiable information (Social Security Numbers) — significant regulatory risk under CCPA, GDPR, HIPAA, and other privacy laws.
  • This specific endpoint (/api/v1/employees/96/ssn) is NOT listed among the provider's publicly advertised APIs, raising questions about its legitimacy or intended audience.
  • No request or response schema is documented anywhere; integration requires blind experimentation.
  • All documentation pages (docs, API, pricing, README) returned only a 'Connect wallet' prompt with no usable content.
  • Hardcoded employee ID (96) in the URL — unclear if other employee IDs are accessible or if this is a demo.

Citations

Provenance

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

Agent access