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 (specifically employee record #82) 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 provider lowpaymentfee.com hosts a broader suite 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 priced at $0.02 per request with no API keys, no rate limits, and no minimum commitments required. Payment is handled entirely through the x402 protocol on the Base L2 network.

The specific endpoint `/api/v1/employees/82` appears to serve a single employee record. No OpenAPI schema, detailed documentation, or response examples were found in the crawl — the docs, pricing, and API pages all returned only a "Connect wallet" prompt with no substantive content. The exact fields returned in the employee JSON response are unknown.

Capabilities

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

Use cases

  • Retrieving employee record data on-demand with per-call USDC micropayments
  • Integrating employee information into agent workflows without API key management
  • Demonstrating x402 payment protocol integration for data access

Fit

Best for

  • Developers experimenting with x402 pay-per-call patterns
  • Agents needing on-demand employee data without subscription commitments
  • Low-volume data retrieval where per-request pricing is cost-effective

Not for

  • High-volume bulk employee data exports (no batch endpoint documented)
  • Use cases requiring detailed schema documentation or SLA guarantees
  • Applications needing employee search or filtering (this serves a single fixed record)

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.35/ 1.00

The endpoint is live and returns a valid x402 402 challenge with clear pricing. However, there is no OpenAPI schema, no response examples, no documentation beyond a wallet-connect prompt, and the purpose of the employee data endpoint is unclear. The listing is essentially a stub with confirmed liveness and pricing.

Warnings

  • No OpenAPI or schema documentation available — response format is unknown
  • Docs, pricing, and API pages all render only 'Connect wallet' with no substantive content
  • The endpoint serves a single hardcoded employee record (#82); unclear if other IDs are supported
  • No information on what fields the employee record contains

Citations

Provenance

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

Agent access