x402basequality 0.30

Transaction receipt endpoint on Base, paid per-call via x402 with USDC.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com provides a transaction receipt resource at `/api/v1/transactions/279/receipt`. It is part of a broader platform that offers multiple x402-gated API categories including data & analytics, AI & machine learning, finance & Web3, and infrastructure utilities — all priced at $0.02 per request and settled in USDC on the Base network.

The specific endpoint probed returns a 402 challenge requesting payment of up to 20,000 base units of USDC (0x8335…2913 on Base, 6 decimals = $0.02) via the x402 "exact" scheme. Payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout. The endpoint accepts POST requests and returns `application/json`.

The platform advertises no API keys, no rate limits, and instant access. However, documentation pages (`/docs`, `/pricing`, `/api`, `/README`) all resolve to a minimal "Connect wallet" prompt with no further technical detail. There is no OpenAPI spec, no request/response schema, and no example payloads available. The actual data returned by this receipt endpoint — and indeed by most endpoints on the platform — is undocumented, so callers must discover behavior empirically.

Capabilities

x402-paymentusdc-settlementbase-networkper-call-pricingtransaction-receiptjson-response

Use cases

  • Retrieving a transaction receipt via a single paid API call
  • Demonstrating x402 payment flow integration on Base
  • Agent-driven micropayment workflows for on-chain data

Fit

Best for

  • Developers experimenting with x402 payment protocol
  • Agents that need pay-per-call access without API keys
  • Low-cost per-request data retrieval on Base

Not for

  • Production workloads requiring documented request/response schemas
  • Use cases needing bulk or subscription-based pricing
  • Users who cannot pay in USDC on Base network

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/transactions/279/receipt
# Returns 402 with x402 challenge; attach X-PAYMENT header with valid payment to receive the receipt.

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge with clear pricing ($0.02 USDC on Base). However, there is no OpenAPI spec, no documented request/response schema, no examples, and all documentation pages are empty stubs. The purpose of this specific receipt endpoint is unclear beyond its URL path.

Warnings

  • No OpenAPI or schema documentation available — all doc pages return only a 'Connect wallet' stub.
  • The actual response payload for this receipt endpoint is completely undocumented.
  • The platform lists many endpoint categories but none have published technical documentation.
  • It is unclear what transaction ID 279 refers to or whether the receipt endpoint is parameterized.

Citations

Provenance

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

Agent access