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 141) 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 a broad catalog of other endpoints spanning data analytics, AI/ML inference, finance, and utility services, all at the same price point.

Documentation is extremely sparse — the /docs, /pricing, /api, and /README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no request/response examples, and no description of what fields the response contains beyond the endpoint path implying it returns an SSN for employee 141. The endpoint is live (returns 402 challenge as expected for x402).

Capabilities

x402-paymentusdc-base-networkemployee-data-lookupssn-retrievalper-request-micropaymentjson-response

Use cases

  • Retrieving SSN data for a specific employee record via automated agent payment
  • Integrating employee identity verification into payroll or HR workflows
  • Demonstrating x402 micropayment protocol for sensitive data access

Fit

Best for

  • Agents needing on-demand access to employee PII behind a paywall
  • Developers experimenting with x402 payment protocol on Base
  • Automated workflows requiring SSN data without API key provisioning

Not for

  • Bulk employee data retrieval (endpoint is scoped to a single employee ID)
  • Use cases requiring detailed documentation or schema guarantees before integration
  • Scenarios where handling PII (SSN) raises regulatory compliance concerns you haven't addressed

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/employees/141/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 with clear pricing. However, documentation is essentially nonexistent — no OpenAPI spec, no request/response schema, no examples, and the endpoint path suggests it returns highly sensitive PII (SSN) for a hardcoded employee ID with no explanation of the data source or legitimacy. This is effectively a stub listing.

Warnings

  • Endpoint appears to serve Social Security Number (SSN) data, which is highly regulated PII — verify legal compliance before use.
  • No documentation, OpenAPI schema, or response examples are available; the docs pages only show 'Connect wallet'.
  • Endpoint path is hardcoded to employee ID 141; unclear if other employee IDs are supported or what the data source is.
  • The legitimacy and provenance of the employee/SSN data is completely unknown.
  • No robots.txt or agents.txt present on the origin.

Citations

Provenance

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

Agent access