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 retrieval API. When called via POST, it returns a JSON receipt for transaction ID 7. Payment is settled on the Base network using USDC (contract 0x8335…2913) through the x402 exact-payment scheme.
The endpoint is part of a broader platform (lowpaymentfee.com) that advertises multiple API categories including Data & Analytics, AI & Machine Learning, Finance & Web3, and Infrastructure utilities — all priced at $0.02 per request. The platform emphasizes simplicity: no API keys, no rate limits, and no minimum commitments. Payment is handled entirely through the x402 protocol's X-PAYMENT header.
The specific endpoint probed (/api/v1/transactions/7/receipt) charges a maximum of 20,000 base units of USDC (6 decimals), which equals $0.02 per call. The x402 challenge is live and returns a well-formed v1 challenge with a 300-second payment timeout. Documentation on the site is extremely thin — the docs, pricing, API, 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 usage examples available from the crawled pages.
Capabilities
Use cases
- —Retrieving transaction receipts programmatically with per-call USDC payment
- —Integrating pay-per-use APIs into agent workflows without API key management
- —Demonstrating x402 protocol payment flows on Base network
Fit
Best for
- —Agents or services that need on-demand transaction receipt data with no subscription
- —Developers experimenting with x402 protocol integrations on Base
- —Workflows requiring keyless, pay-as-you-go API access
Not for
- —Users needing detailed API documentation or OpenAPI specs before integration
- —High-volume batch processing where per-call pricing may add up
- —Users without access to USDC on Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/7/receipt \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The x402 challenge is live and well-formed, confirming the endpoint works. However, documentation is essentially nonexistent — docs, pricing, API, and README pages all show only 'Connect wallet'. There is no OpenAPI spec, no request/response schema, and no examples. The endpoint path suggests a hardcoded transaction ID (7), making the general utility unclear.
Warnings
- —Documentation pages (docs, pricing, API, README) contain no substantive content — only a 'Connect wallet' prompt
- —No OpenAPI or schema documentation available for request or response formats
- —The endpoint path includes a hardcoded transaction ID (/transactions/7/receipt); it is unclear whether other transaction IDs are supported or what the broader API surface looks like
- —The platform advertises many API categories (AI, analytics, finance, utilities) but no details on actual functionality are documented
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/transactions/7/receipt
- —The platform advertises $0.02 per request pricing with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/transactions/7/receipt
- —Multiple API categories are listed including Data & Analytics, AI & ML, Finance & Web3, and Infrastructurehttps://lowpaymentfee.com