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 #43) 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. Payments are made inline via the x402 protocol's X-PAYMENT header.

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 employee endpoint accepts or returns. The endpoint is confirmed live (returns a proper 402 challenge), but the actual data content and input parameters are unknown.

Capabilities

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

Use cases

  • Retrieving employee record data with per-call USDC micropayments
  • Integrating employee data into agent workflows without API key management
  • Programmatic access to employee information settled on Base L2

Fit

Best for

  • Agents needing keyless, pay-per-call access to employee data
  • Developers experimenting with x402 payment protocol integrations
  • Use cases requiring no rate limits and no subscription commitments

Not for

  • Production systems requiring well-documented request/response schemas
  • Bulk employee data retrieval (pay-per-call at $0.02 adds up at scale)
  • Users who need traditional API key authentication or OAuth

Quick start

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

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. However, there is no OpenAPI schema, no documentation of request parameters or response format, and all doc pages are empty stubs. The actual data returned is completely unknown, making this effectively a stub listing.

Warnings

  • No documentation available — /docs, /pricing, /api, and /README pages all show only 'Connect wallet' with no content
  • No OpenAPI or request/response schema provided; input parameters and output fields are unknown
  • The specific purpose of the /employees/43 endpoint (what employee data it returns) is not documented anywhere
  • This endpoint targets a single hardcoded employee ID (43); it is unclear if other IDs are available or how to discover them

Citations

Provenance

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

Agent access