x402basequality 0.30

Pay-per-call employee data API on Base via x402, settled in USDC at $0.02/request.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com provides access to employee data (specifically employee record #155) via the x402 payment protocol. It accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x8335…2913) with a maximum cost of 20,000 base units, which equals $0.02 per request (USDC uses 6 decimals).

The endpoint is part of a broader platform (lowpaymentfee.com) that offers multiple API categories including Data & Analytics, AI & Machine Learning, Finance & Web3, and Infrastructure utilities — all priced at $0.02 per request. The platform advertises no API keys, no rate limits, and instant access. All payments flow through the x402 protocol on the Base L2 network.

Documentation is extremely sparse. The crawled /docs, /api, /pricing, 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 fields the employee record contains or what input parameters the POST body expects. The endpoint is confirmed live (returns a proper 402 challenge), but the actual data contract is unknown.

Capabilities

x402-paymentusdc-settlementbase-networkemployee-datajson-responsepay-per-callno-api-key

Use cases

  • Retrieving employee record data on a per-call payment basis without needing an API key
  • Agent-driven workflows that need to fetch structured employee information and can pay per request via x402
  • Demonstrating x402 protocol integration for micropayment-gated REST APIs

Fit

Best for

  • Developers experimenting with x402 payment protocol on Base
  • Agents that need keyless, pay-per-call access to data endpoints
  • Use cases where $0.02/request micropayments are preferable to subscription billing

Not for

  • Production systems requiring documented request/response schemas and SLAs
  • Bulk employee data retrieval where per-call pricing would be cost-prohibitive
  • Users without USDC on the Base network

Quick start

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

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, but there is no documentation, no OpenAPI spec, no request/response schema, and no examples. The crawled docs pages are all empty stubs. The actual data contract (what fields are returned, what POST body is expected) is completely unknown.

Warnings

  • No documentation available — all doc pages return only a 'Connect wallet' prompt with no content
  • No OpenAPI or schema definition; request body format and response structure are unknown
  • The specific endpoint path (/api/v1/employees/155) suggests a hardcoded resource ID; unclear if this is a demo or production data
  • No information about what 'employee' data is served or its source

Citations

Provenance

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

Agent access