Pay-per-call transaction receipt endpoint on Base via x402, settled in USDC at $0.02/request.
What it does
This x402-enabled endpoint at lowpaymentfee.com provides a transaction receipt for transaction ID 227 via a POST request. It is part of a broader platform offering multiple API categories — data & analytics, AI & machine learning, finance & Web3, and infrastructure utilities — all priced at $0.02 per request with no API keys, no rate limits, and no commitments required. Payment is settled on the Base network using USDC (USD Coin).
The specific endpoint `/api/v1/transactions/227/receipt` returns a JSON response (MIME type `application/json`) upon successful payment. The x402 challenge confirms the endpoint is live, accepting an exact payment scheme with a max amount of 20,000 base units of USDC (6 decimals), which equals $0.02. The payment timeout is 300 seconds. No OpenAPI schema, detailed documentation, or example responses were found in the crawl — the docs, pricing, API, and README pages all rendered only a "Connect wallet" prompt with no substantive content.
Because this endpoint is scoped to a single transaction ID (227), its general utility is unclear. It may be a demonstration or template endpoint rather than a broadly useful API. The platform lists many other endpoints across various domains, but this specific listing covers only the receipt retrieval for transaction 227.
Capabilities
Use cases
- —Retrieving a receipt for a specific transaction via programmatic pay-per-call access
- —Demonstrating x402 payment protocol integration on the Base network
- —Agent-driven workflows that need to fetch transaction documentation without API key provisioning
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents needing keyless, pay-per-call access to transaction receipts
- —Projects already operating on the Base L2 network with USDC
Not for
- —Bulk retrieval of many different transaction receipts (endpoint is scoped to transaction 227)
- —Users who need detailed API documentation or OpenAPI specs before integrating
- —Applications requiring non-USDC or non-Base-network payment rails
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/227/receipt \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02 USDC on Base), but there is no OpenAPI schema, no example request/response, and no meaningful documentation — all doc pages returned only 'Connect wallet'. The endpoint is also scoped to a single transaction ID, limiting general utility.
Warnings
- —No OpenAPI or schema documentation available; all doc pages render only 'Connect wallet'
- —Endpoint is scoped to a single transaction ID (227) — unclear if this is a template or a fixed resource
- —No example responses available; response format is unknown beyond MIME type application/json
- —Platform appears to be a demonstration or early-stage project with many listed endpoints but no substantive docs
Citations
- —The endpoint returns a 402 challenge with x402Version 1, accepting USDC on Base network with maxAmountRequired of 20000 base units ($0.02)https://lowpaymentfee.com/api/v1/transactions/227/receipt
- —Platform lists APIs across data & analytics, AI & ML, finance & Web3, and infrastructure categories, all at $0.02/requesthttps://lowpaymentfee.com
- —Pricing is $0.02/request with no API keys, no rate limits, instant access, on Base networkhttps://lowpaymentfee.com
- —USDC asset address is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/transactions/227/receipt