x402basequality 0.30

Pay-per-call transaction receipt 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/transactions/290/receipt

What it does

This x402-enabled endpoint at lowpaymentfee.com provides access to a transaction receipt resource (transaction ID 290) via a POST request. Payment is settled on the Base network using USDC (contract 0x8335…2913) through the x402 exact payment scheme. The advertised cost is $0.02 per request (20,000 base units of USDC with 6 decimals).

The provider's landing page lists a broad catalog of pay-per-call APIs spanning data & analytics (metrics, reports, data export, insights), AI & machine learning (sentiment analysis, text summarization, classification, embeddings), finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation) — all priced at $0.02 per request with no API keys, no rate limits, and no commitments. However, the specific endpoint being listed here is `/api/v1/transactions/290/receipt`, which appears to be a transaction receipt retrieval resource rather than one of the catalog items shown on the homepage.

Documentation is extremely sparse — the /docs, /api, /pricing, 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 endpoint is confirmed live (returns a proper 402 x402 challenge), but the actual response format and required POST body are unknown.

Capabilities

x402-paymentusdc-settlementbase-networktransaction-receiptpay-per-callno-api-key

Use cases

  • —Retrieving a transaction receipt for transaction 290 via a paid API call
  • —Demonstrating x402 payment protocol integration on Base
  • —Agent-driven pay-per-call data retrieval without API key management

Fit

Best for

  • —Developers experimenting with x402 payment protocol
  • —Agents that need keyless, pay-per-call API access on Base
  • —Projects requiring USDC-settled micropayment endpoints

Not for

  • —Production workloads requiring documented request/response schemas
  • —Bulk or high-volume data retrieval where per-call pricing is inefficient
  • —Users who need traditional API key authentication or OAuth flows

Quick start

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

Endpoint

URLhttps://lowpaymentfee.com/api/v1/transactions/290/receipt
Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is confirmed live with a valid 402 x402 challenge, but there is no documentation, no OpenAPI spec, no request/response examples, and the docs pages are empty. The specific resource (transaction 290 receipt) is not explained anywhere on the site. This is effectively a stub listing.

Warnings

  • —No OpenAPI spec or schema documentation available
  • —All documentation pages (/docs, /api, /pricing, /README) render only 'Connect wallet' with no content
  • —The specific endpoint /api/v1/transactions/290/receipt is not listed in the provider's homepage catalog — its purpose and response format are unknown
  • —No request body schema or response schema documented anywhere
  • —The endpoint appears to be for a single hardcoded transaction ID (290), which may indicate a demo or test resource

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-19 13:01:32Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-24

Agent access

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