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 (employee ID 52) behind an x402 paywall. The endpoint accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x8335…2913) with a maximum cost of $0.02 per request (20,000 base units at 6 decimals).

The provider lowpaymentfee.com hosts a broad catalog of x402-gated APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services, all priced at $0.02 per call. No API keys or rate limits are advertised; access is granted purely via the x402 payment header. The site states "pay only for what you use" with no minimums or commitments.

This specific endpoint is narrowly scoped: it serves SSN data for a single employee record. There is no documentation on request body schema, available query parameters, or the structure of the response beyond the MIME type (application/json). The endpoint's nature — returning personally identifiable information (SSN) — raises significant regulatory and ethical concerns. Prospective consumers should verify that their use complies with applicable privacy laws (e.g., FCRA, state SSN protection statutes, GDPR if applicable).

Capabilities

x402-paymentusdc-baseemployee-datassn-lookupjson-responseno-api-keyper-request-pricing

Use cases

  • Retrieving SSN for a known employee record in an authorized payroll or HR workflow
  • Demonstrating x402 micropayment integration on Base network
  • Testing pay-per-call API patterns with low-cost endpoints

Fit

Best for

  • Developers experimenting with x402 payment protocol on Base
  • Authorized HR or payroll systems needing on-demand SSN retrieval
  • Agent-based workflows that settle per-call payments in USDC

Not for

  • Bulk PII harvesting or unauthorized background checks
  • Use cases requiring compliance certifications (SOC 2, HIPAA) — no evidence the provider holds any
  • Production systems needing documented response schemas or SLAs

Quick start

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

Example

Request

{
  "url": "https://lowpaymentfee.com/api/v1/employees/52/ssn",
  "method": "POST",
  "headers": {
    "X-PAYMENT": "<x402_payment_token>",
    "Content-Type": "application/json"
  }
}

Endpoint

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), but there is no documentation on request/response schemas, no OpenAPI spec, no example responses, and the docs/pricing/README pages are all blank ('Connect wallet' only). The endpoint serves highly sensitive PII with no visible compliance or authorization framework.

Warnings

  • Endpoint returns personally identifiable information (SSN) — verify legal compliance before use.
  • No response schema or example response is documented anywhere.
  • All documentation pages (docs, pricing, README, api) render only 'Connect wallet' with no substantive content.
  • No evidence of security certifications, access controls, or audit logging for PII access.
  • Endpoint is hardcoded to employee ID 52 — unclear if other employee IDs are supported or if this is a demo.

Citations

Provenance

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

Agent access