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 "Premium API Access" receipt for transaction ID 306. It is part of a broader platform offering dozens of pay-per-call API endpoints spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all priced at $0.02 per request and settled in USDC on the Base network.
The specific endpoint `/api/v1/transactions/306/receipt` accepts POST requests and returns JSON. Payment is handled via the x402 protocol: callers attach an X-PAYMENT header containing a signed USDC payment of up to 20,000 base units (i.e., $0.02, since USDC uses 6 decimals). The payment is sent to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` on Base mainnet, using the USDC contract at `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`. No API keys or rate limits are advertised; access is gated purely by payment.
Documentation is extremely sparse — the docs, pricing, and API pages all render only a "Connect wallet" prompt with no additional technical detail. There is no OpenAPI spec, no request/response schema documentation, and no example payloads available. The endpoint is confirmed live (returns a proper 402 challenge), but the actual response format and the meaning of "transaction 306 receipt" are not documented anywhere in the crawled material.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 306 via a single paid API call
- —Demonstrating x402 protocol payment flows on Base with USDC
- —Integrating pay-per-call APIs into agent workflows without API key management
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents needing keyless, pay-per-call API access on Base
- —Projects requiring USDC-settled micropayment endpoints
Not for
- —Production use cases requiring documented request/response schemas
- —Bulk or high-volume data retrieval (no batch endpoints documented)
- —Users who need fiat or non-crypto payment options
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/306/receipt \
-H "X-PAYMENT: <x402-signed-payment-header>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is confirmed live with a valid 402 challenge, but documentation is essentially nonexistent — docs/pricing/API pages all show only 'Connect wallet'. There is no OpenAPI spec, no request/response schema, no examples, and the purpose of 'transaction 306 receipt' is unexplained. The listing is effectively a stub.
Warnings
- —No documentation available beyond the landing page listing — docs, pricing, and API pages render only 'Connect wallet'
- —No OpenAPI or schema definition for request or response payloads
- —The specific meaning of 'transactions/306/receipt' is undocumented; it is unclear what data this endpoint returns
- —The broader platform lists many endpoints but none have documented schemas or examples
Citations
- —Endpoint returns 402 with x402 challenge advertising USDC payment on Base networkhttps://lowpaymentfee.com/api/v1/transactions/306/receipt
- —Platform advertises $0.02 per request across all endpoints with no API keys, no rate limitshttps://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/transactions/306/receipt
- —Docs, pricing, and API pages render only 'Connect wallet' with no additional contenthttps://lowpaymentfee.com/docs