Transaction receipt endpoint on Base, paid per-call via x402 with USDC.
What it does
This endpoint at lowpaymentfee.com provides a transaction receipt resource at `/api/v1/transactions/366/receipt`. It is part of a broader platform that offers multiple API categories including data & analytics, AI & machine learning, finance & Web3, and infrastructure utilities — all payable per-request via the x402 protocol on the Base network using USDC.
The specific endpoint probed returns a 402 challenge requesting payment of up to 20,000 base units of USDC (0.02 USD, since USDC uses 6 decimals) to the address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3`. The payment scheme is "exact" on the Base L2 network, with a timeout of 300 seconds. The endpoint accepts POST requests and returns `application/json`.
The platform advertises a flat $0.02 per request across all its endpoints, with no API keys, no rate limits, and no minimum commitments. However, documentation pages (docs, pricing, README) all resolve to minimal "Connect wallet" stubs, so there is no detailed API documentation, request/response schemas, or usage examples available. The specific purpose of the `/transactions/366/receipt` endpoint — whether it retrieves a receipt for a prior transaction or generates one — is not documented beyond the generic "Premium API Access" label.
Capabilities
Use cases
- —Retrieving a transaction receipt by paying a micro-fee in USDC on Base
- —Integrating pay-per-call infrastructure into agent workflows without API keys
- —Demonstrating x402 protocol payment flows for Base L2 USDC transactions
Fit
Best for
- —Developers experimenting with x402 payment protocol on Base
- —Agents that need keyless, pay-per-request API access
- —Low-cost micro-transaction receipt retrieval
Not for
- —Production workloads requiring detailed API documentation and SLAs
- —Use cases needing non-crypto payment methods
- —Bulk or high-volume receipt retrieval where per-call fees add up
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/366/receipt
# Returns 402 with x402 payment challenge; attach X-PAYMENT header with signed USDC payment to proceed.Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge, but there is no API documentation, no request/response schema, and the purpose of this specific endpoint is unclear beyond the generic 'Premium API Access' label. All doc pages resolve to empty 'Connect wallet' stubs.
Warnings
- —No API documentation available — all doc pages show only 'Connect wallet'
- —No request or response schema provided for this endpoint
- —The specific function of /api/v1/transactions/366/receipt is undocumented
- —The hardcoded transaction ID '366' in the path suggests this may be a single-resource endpoint rather than a parameterized one
Citations
- —The endpoint returns a 402 challenge requesting up to 20,000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/transactions/366/receipt
- —Platform advertises $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/transactions/366/receipt
- —Documentation, pricing, and README pages all resolve to minimal 'Connect wallet' contenthttps://lowpaymentfee.com/docs