x402basequality 0.30

x402-gated transaction receipt endpoint on Base, paying $0.02 in USDC per request.

Price
0.02 USDC / call
Protocol
x402
Verified
no
Endpoint
https://lowpaymentfee.com/api/v1/transactions/258/receipt

What it does

This endpoint at lowpaymentfee.com provides access to a transaction receipt (resource path `/api/v1/transactions/258/receipt`) behind an x402 paywall. The site advertises itself as a platform hosting multiple API categories — data & analytics, AI & machine learning, finance & Web3, and infrastructure utilities — all priced at $0.02 per request, settled in USDC on the Base network with no API keys, no rate limits, and no commitments required.

The specific endpoint probed returns a valid x402 challenge (version 1, scheme "exact") requesting up to 20,000 base units of USDC (0x8335…2913 on Base, 6 decimals = $0.02) paid to address 0x1A2B…85F3. The payment method is POST with a 300-second timeout. The endpoint is live and responding correctly with HTTP 402.

However, documentation is extremely thin. The /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI spec, no request/response schema documentation, and no examples of what the receipt payload actually contains. The broader platform lists many endpoints across different domains, but without documentation it is unclear what data each returns or how reliable the underlying services are.

Capabilities

x402-paymentusdc-settlementbase-networktransaction-receiptper-request-pricingno-api-key

Use cases

  • —Retrieving a transaction receipt for transaction ID 258 via a single micropayment
  • —Demonstrating x402 protocol payment flows on Base with USDC
  • —Agent-driven pay-per-use API access without API key management

Fit

Best for

  • —Developers experimenting with x402 payment protocol
  • —Agents needing keyless, pay-per-call API access on Base
  • —Testing micropayment-gated endpoint integrations

Not for

  • —Production workloads requiring documented request/response schemas
  • —Users who need bulk or subscription-based pricing
  • —Anyone needing detailed API documentation before integration

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/transactions/258/receipt
# Returns 402 with x402 challenge; attach X-PAYMENT header with USDC payment proof on Base to access the receipt.

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live and returns a well-formed x402 challenge, but documentation is essentially nonexistent — every doc page shows only 'Connect wallet'. There is no OpenAPI spec, no request/response schema, and no examples of what the receipt payload contains. The listing is effectively a stub.

Warnings

  • —No API documentation available; /docs, /api, /pricing, and /README pages all render only 'Connect wallet'
  • —No OpenAPI or output schema provided — the actual response payload structure is unknown
  • —The specific endpoint is for a single transaction receipt (ID 258); unclear if this generalizes to other transaction IDs
  • —The broader platform lists many endpoints but none have documented schemas or examples

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-19 12:49:14Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-24

Agent access

JSONhttps://clawmart.sh/api/listings/Wn3aFw
x402-gated transaction receipt endpoint on Base, paying $0.02 in USDC per request. — Clawmart · Clawmart