x402basequality 0.35

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

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

What it does

This endpoint at lowpaymentfee.com provides a transaction receipt resource at `/api/v1/transactions/380/receipt`. It is part of a broader platform that offers a variety of pay-per-request APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all settled via the x402 protocol on the Base network using USDC.

The specific endpoint probed returns an x402 challenge requesting up to 0.02 USDC (20,000 base units of USDC with 6 decimals) per call, consistent with the site's advertised flat $0.02/request pricing. Payment is made via the x402 "exact" scheme to a designated wallet address, 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. Documentation pages (`/docs`, `/pricing`, `/api`, `/README`) all resolve but contain only a "Connect wallet" prompt with no substantive technical documentation. There is no OpenAPI spec, no request/response schema beyond the x402 challenge's `outputSchema`, and no example payloads. The actual data returned by this receipt endpoint is unknown — it likely returns details about transaction #380, but the response format is not documented.

Capabilities

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

Use cases

  • —Retrieving a transaction receipt for transaction #380 via a micropayment-gated endpoint
  • —Demonstrating x402 protocol payment flows on Base with USDC
  • —Integrating pay-per-request APIs without API key management

Fit

Best for

  • —Developers experimenting with x402 payment protocol integrations
  • —Agents that need to fetch transaction receipts via crypto micropayments
  • —Projects requiring keyless, pay-as-you-go API access on Base

Not for

  • —Users needing detailed API documentation or response schemas before integrating
  • —High-volume batch retrieval where per-request fees add up quickly
  • —Anyone without a Base-compatible USDC wallet

Quick start

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

Endpoint

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

Quality

0.35/ 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 or response schema, no examples, and all documentation pages are empty stubs showing only 'Connect wallet'. The purpose of this specific receipt endpoint is unclear beyond its URL path.

Warnings

  • —No OpenAPI or schema documentation available — response format is entirely unknown
  • —All documentation pages (/docs, /pricing, /api, /README) return only a 'Connect wallet' stub with no content
  • —The specific resource (transaction 380 receipt) is opaque — unclear what data is returned or what input is expected in the POST body
  • —The broader platform lists many API categories (AI, analytics, finance, utilities) but none have documented schemas

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/y3eBY8
Transaction receipt endpoint on Base, paid per-call via x402 with USDC. — Clawmart · Clawmart