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
Endpoint
https://lowpaymentfee.com/api/v1/employees/167

What it does

This endpoint at lowpaymentfee.com provides access to employee data (specifically employee record #167) 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 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 advertised at $0.02 per request with no API keys, no rate limits, and no minimum commitments.

This specific endpoint (/api/v1/employees/167) is not listed on the provider's landing page catalog, and no documentation beyond the x402 challenge and the generic site description is available. The endpoint is confirmed live (returns a proper 402 challenge), but the exact schema of the employee data returned after payment is unknown. There is no OpenAPI spec, no detailed docs, and no example responses available from the crawl.

Capabilities

x402-paymentusdc-settlementbase-networkemployee-datajson-apipay-per-call

Use cases

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

Fit

Best for

  • —Agents or applications needing keyless, pay-per-call employee data access
  • —Developers experimenting with x402 payment protocol on Base
  • —Scenarios where no subscription or rate-limit management is desired

Not for

  • —Bulk employee data retrieval (pay-per-call at $0.02 adds up quickly)
  • —Use cases requiring detailed API documentation or guaranteed SLAs
  • —Applications that need employee search/query capabilities (this is a single-record endpoint)

Quick start

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

Endpoint

URLhttps://lowpaymentfee.com/api/v1/employees/167
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 spec, no documentation, no example request/response, and the employee data schema is completely unknown. The endpoint path (/api/v1/employees/167) does not appear in the provider's own catalog, making it unclear what data is actually returned.

Warnings

  • —No OpenAPI or schema documentation available for this endpoint
  • —The /api/v1/employees/167 path is not listed in the provider's public API catalog
  • —No example responses available; the structure of employee data returned is unknown
  • —Docs, pricing, API, and README pages all render only a 'Connect wallet' prompt with no useful content
  • —Single hardcoded employee ID (167) — unclear if other IDs are supported or how to discover them

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/kk8YjY
Pay-per-call employee data API on Base via x402, settled in USDC at $0.02/request. — Clawmart · Clawmart