Pay-per-call transaction receipt endpoint on Base via x402, settling in USDC at $0.02/request.
What it does
This x402-enabled endpoint at lowpaymentfee.com provides access to a transaction receipt resource (transaction ID 379) via a POST request. Payment is settled on the Base network using USDC (contract 0x8335…2913) through the x402 exact-payment scheme. The price per call is $0.02 (20,000 base units of USDC with 6 decimals).
The broader lowpaymentfee.com platform advertises a suite of pay-per-request APIs spanning data & analytics (metrics, reports, data export, insights), AI & machine learning (sentiment analysis, text summarization, classification, embeddings), finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints are listed at $0.02 per request with no API keys, no rate limits, and no minimum commitments required.
The specific endpoint being listed here — `/api/v1/transactions/379/receipt` — appears to return a receipt for a particular transaction. Documentation beyond the landing page is essentially empty (all sub-pages only show a "Connect wallet" prompt), so the exact request body schema and response format are unknown. The endpoint is confirmed live, returning a proper 402 challenge with x402 version 1.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 379 via a single paid API call
- —Demonstrating x402 payment flow integration for agent-to-service commerce
- —Programmatic access to transaction data without traditional API key provisioning
Fit
Best for
- —Developers experimenting with x402 payment protocol on Base
- —Agents needing keyless, pay-per-call access to transaction data
- —Projects requiring USDC-settled micropayment API interactions
Not for
- —Bulk retrieval of many different transaction receipts (only transaction 379 is exposed at this URL)
- —Users who need detailed API documentation or OpenAPI schemas before integrating
- —Applications requiring sub-cent pricing or free-tier access
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/379/receipt \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is confirmed live with a valid 402 challenge, but documentation is essentially nonexistent — all doc/pricing/API pages only render a wallet-connect prompt. There is no OpenAPI schema, no example request/response, and the specific purpose of this single-transaction receipt endpoint is unclear. The listing is largely inferred from the x402 challenge and the landing page.
Warnings
- —Documentation pages (/docs, /api, /pricing, /README) all return only a 'Connect wallet' prompt with no actual content.
- —No OpenAPI or request/response schema is available; input and output formats are unknown.
- —This endpoint is scoped to a single transaction ID (379); it is unclear whether other transaction IDs are available at different URLs.
- —The platform advertises many API categories on its landing page, but none of them could be verified beyond the landing page listing.
Citations
- —The endpoint returns a 402 challenge with x402 version 1, accepting USDC on Base network with maxAmountRequired of 20000 base units.https://lowpaymentfee.com/api/v1/transactions/379/receipt
- —All APIs are listed at $0.02 per request with no API keys, no rate limits, and instant access on the Base network.https://lowpaymentfee.com
- —The platform advertises APIs across Data & Analytics, AI & Machine Learning, Finance & Web3, and Infrastructure categories.https://lowpaymentfee.com
- —USDC asset contract address is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base.https://lowpaymentfee.com/api/v1/transactions/379/receipt