x402basequality 0.35

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 records via the x402 payment protocol. The specific resource `/api/v1/employees/100` returns JSON data for employee ID 100 when called with a POST request and a valid X-PAYMENT header containing a USDC micropayment on the Base network.

The endpoint is part of a broader platform (lowpaymentfee.com) that offers numerous pay-per-call APIs spanning data & analytics, AI & machine learning (sentiment analysis, summarization, classification, embeddings), finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints on the platform are priced at $0.02 per request, paid in USDC on Base with no API keys, no rate limits, and no minimum commitments.

The x402 challenge confirms the endpoint is live, accepting payments to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` using USDC (contract `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`) on the Base network. The max amount required is 20,000 base units, which equals $0.02 given USDC's 6 decimals. The timeout for payment settlement is 300 seconds. No OpenAPI schema or detailed documentation was found beyond the landing page listing; the docs, API, pricing, and README pages all returned only a "Connect wallet" prompt with no substantive content.

Capabilities

x402-paymentusdc-baseemployee-datapay-per-callno-api-keyjson-response

Use cases

  • Retrieving employee records on-demand with per-call USDC micropayments
  • Integrating employee data into agent workflows without managing API keys
  • Demonstrating x402 payment protocol integration for data access

Fit

Best for

  • Developers experimenting with x402 payment protocol
  • Agents needing keyless, pay-per-call data access
  • Low-volume or sporadic employee data lookups

Not for

  • High-volume bulk employee data exports (no documented batch endpoint)
  • Users who need detailed API documentation or OpenAPI specs before integrating
  • Applications requiring non-crypto payment methods

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.35/ 1.00

The x402 challenge is live and pricing is clear ($0.02 USDC on Base), but there is no OpenAPI schema, no response examples, no documentation beyond a landing page, and the specific data returned by the employees endpoint is entirely undocumented. The docs/pricing/README pages are all blank wallet-connect stubs.

Warnings

  • No OpenAPI or schema documentation available for this endpoint
  • Response format and fields for /api/v1/employees/100 are completely undocumented
  • All secondary pages (docs, pricing, README, api) return only a 'Connect wallet' stub with no content
  • The nature and source of the 'employee' data is unclear — could be sample/demo data

Citations

Provenance

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

Agent access

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