x402-gated transaction receipt endpoint on Base, paid per-call in USDC.
What it does
This endpoint at lowpaymentfee.com provides access to a specific transaction receipt (transaction 351) behind an x402 paywall. The broader lowpaymentfee.com platform advertises a suite of pay-per-request APIs spanning data & analytics, AI & machine learning (sentiment analysis, summarization, classification, embeddings), finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints are priced at $0.02 per request, settled in USDC on the Base network, with no API keys, no rate limits, and no minimum commitments.
The specific endpoint probed — `/api/v1/transactions/351/receipt` — returned a valid x402 challenge with a `maxAmountRequired` of 20,000 base units of USDC (0x8335… on Base), which equals $0.02 given USDC's 6 decimals. The payment scheme is "exact" with a 300-second timeout. The endpoint accepts POST requests and returns `application/json`. No OpenAPI spec, detailed documentation, or response schema was found during crawling; the docs, pricing, API, and README pages all rendered only a "Connect wallet" prompt with no substantive content.
Because this is a single transaction receipt endpoint rather than a general-purpose API, its utility to agents is narrow unless it is representative of a broader pattern (e.g., any `/api/v1/transactions/{id}/receipt` path). The platform's landing page suggests a much wider API surface, but none of those other endpoints were probed or documented with schemas.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 351 via a single micropayment
- —Demonstrating x402 payment flow on Base with USDC
- —Programmatic access to paid API endpoints without API key management
Fit
Best for
- —Agents or developers experimenting with x402 payment protocol
- —Accessing pay-per-use endpoints without subscription or API key signup
- —Low-cost single-call data retrieval on Base network
Not for
- —Bulk or high-volume transaction receipt retrieval (no documented batch endpoint)
- —Users who need detailed API documentation or response schemas before integrating
- —Use cases requiring non-USDC or non-Base payment rails
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/351/receipt \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but there is no OpenAPI spec, no response schema, no example responses, and the crawled documentation pages are empty (only 'Connect wallet'). The specific endpoint is a single transaction receipt with no clear general-purpose utility. The broader platform advertises many endpoints but none are documented.
Warnings
- —No OpenAPI or response schema available for this endpoint
- —Documentation pages (docs, pricing, API, README) all render only 'Connect wallet' with no content
- —This endpoint targets a single hardcoded transaction ID (351); unclear if parameterized paths are supported
- —No example responses available; actual response format is unknown
- —The broader platform advertises many API categories but none were probed or documented
Citations
- —The endpoint returns a valid x402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/transactions/351/receipt
- —All endpoints are priced at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —The platform advertises APIs across data & analytics, AI & ML, finance & Web3, and infrastructure categorieshttps://lowpaymentfee.com
- —USDC asset address is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/transactions/351/receipt