x402basequality 0.35

Pay-per-call employee data endpoint 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/79

What it does

This x402-enabled endpoint at lowpaymentfee.com serves employee data (specifically record ID 79) behind a micropayment wall. It uses the x402 "exact" payment scheme on the Base network, accepting USDC (contract 0x8335…2913) with a max amount of 20,000 base units, which equals $0.02 per request (USDC uses 6 decimals). No API keys or rate limits are required — callers simply attach an X-PAYMENT header with a valid x402 payment proof.

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 appear to be priced uniformly at $0.02 per request. However, the specific endpoint being listed here — /api/v1/employees/79 — is not featured on the provider's landing page catalog, and no documentation or schema for its response body was found.

The endpoint is confirmed live: it returns a proper HTTP 402 challenge with x402 version 1 headers. The POST method is specified in the outputSchema. Because no OpenAPI spec, response schema, or detailed documentation was crawled (docs, pricing, and API pages all returned only a "Connect wallet" stub), the exact shape of the response is unknown. Callers should expect a JSON payload describing an employee record, but the fields are unverified.

Capabilities

x402-paymentusdc-micropaymentbase-networkemployee-datapay-per-callno-api-keyjson-response

Use cases

  • —Retrieving employee record data on-demand with per-call USDC micropayments
  • —Integrating pay-as-you-go data access into agent workflows without API key management
  • —Demonstrating x402 payment protocol integration on Base network

Fit

Best for

  • —Developers experimenting with x402 payment protocol
  • —Agents needing keyless, pay-per-call data access
  • —Projects already operating on the Base L2 network with USDC

Not for

  • —Bulk employee data retrieval (single-record endpoint, $0.02 each)
  • —Users who need detailed API documentation or response schema guarantees
  • —Applications requiring non-crypto payment methods

Quick start

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

Endpoint

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

Quality

0.35/ 1.00

The endpoint is live and returns a valid x402 402 challenge, but there is no OpenAPI spec, no response schema, no documentation beyond a stub landing page, and the specific /employees/79 path is not listed in the provider's own catalog. The response shape is entirely unknown.

Warnings

  • —No OpenAPI or response schema available — response format is unknown
  • —The /api/v1/employees/79 endpoint is not listed on the provider's own landing page catalog
  • —All documentation pages (docs, pricing, API, README) returned only a 'Connect wallet' stub with no useful content
  • —Purpose and data content of the employee record endpoint are unverified

Citations

Provenance

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

Agent access

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