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

What it does

This endpoint at lowpaymentfee.com provides access to employee data (specifically employee record #58) 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 broad catalog of pay-per-call APIs spanning data & analytics, AI/ML inference (sentiment, summarization, classification, embeddings), finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints share the same $0.02/request pricing model with no API keys, no rate limits, and no minimum commitments. Payment is handled entirely through the x402 protocol on the Base L2 network.

Documentation is extremely sparse — the /docs, /pricing, /api, and /README pages all render only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI spec, no request/response schema documentation, and no example payloads available. The specific data returned by the /api/v1/employees/58 endpoint is unknown beyond the fact that it serves application/json. The endpoint is confirmed live (returns a valid 402 challenge).

Capabilities

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

Use cases

  • —Retrieving employee data records on demand with per-call USDC micropayments
  • —Agent-driven data access without pre-registration or API key management
  • —Programmatic employee information lookup settled on Base L2

Fit

Best for

  • —Agents needing keyless, pay-as-you-go access to employee data
  • —Developers experimenting with x402 payment protocol integrations
  • —Low-volume or sporadic data lookups where subscription pricing is wasteful

Not for

  • —High-volume bulk employee data exports (no documented batch endpoint)
  • —Users who need detailed API documentation or guaranteed SLAs before integrating

Quick start

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

Endpoint

URLhttps://lowpaymentfee.com/api/v1/employees/58
Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is confirmed live with a valid 402 challenge and clear pricing ($0.02 USDC on Base). However, there is no OpenAPI spec, no request/response schema, no documentation beyond a wallet-connect prompt, and no examples. The purpose of the employees endpoint is opaque — it could be demo/test data. Effectively a stub listing.

Warnings

  • —No API documentation available — /docs, /pricing, /api, and /README pages all show only 'Connect wallet'
  • —No OpenAPI or schema definition; request body and response structure are completely unknown
  • —The /api/v1/employees/58 endpoint may serve demo or placeholder data — purpose is unverified
  • —No robots.txt or agents.txt present

Citations

Provenance

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

Agent access

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