x402basequality 0.30

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

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This x402-enabled endpoint at lowpaymentfee.com serves employee data (specifically record ID 18) behind a micropayment wall. It uses the x402 "exact" payment scheme on the Base network, accepting USDC (contract 0x8335…2913) with a max amount of 20,000 base units, which equals $0.02 per request (USDC has 6 decimals). No API keys or rate limits are required — callers simply attach an X-PAYMENT header with a valid x402 payment proof.

The hosting site lowpaymentfee.com offers a broader catalog of pay-per-call APIs spanning data & analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints are listed at $0.02 per request with the same x402 payment model on Base.

Documentation is extremely sparse — the docs, pricing, API, and README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI schema, no request/response examples, and no description of what fields the /api/v1/employees/18 endpoint actually returns. The endpoint is confirmed live (returns 402 with a valid x402 challenge), but the lack of documentation makes it difficult to know what data to expect or what request body format is needed.

Capabilities

x402-paymentusdc-micropaymentbase-networkemployee-datapay-per-callno-api-keyjson-response

Use cases

  • Retrieving employee record data with per-call USDC micropayments
  • Demonstrating x402 payment protocol integration on Base
  • Agent-driven data retrieval without API key management

Fit

Best for

  • Developers experimenting with x402 payment protocol
  • Agents that need keyless, pay-per-call data access on Base
  • Low-volume lookups where $0.02/request is acceptable

Not for

  • Production use requiring documented schemas and SLAs
  • High-volume bulk employee data retrieval
  • Users without USDC on Base network

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 402 challenge with clear pricing, but there is zero documentation on request format, response schema, or what employee data is returned. Docs pages are empty. No OpenAPI spec or examples exist.

Warnings

  • No documentation available — docs, pricing, API, and README pages all show only 'Connect wallet'
  • No OpenAPI or JSON schema describing request or response format
  • Unknown what fields or data the /employees/18 endpoint actually returns
  • Single hardcoded employee ID (18) — unclear if other IDs are supported
  • Provider site appears to be a demo or early-stage project

Citations

Provenance

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

Agent access