x402-gated transaction receipt endpoint on Base, paid per-call in USDC.
What it does
This endpoint at lowpaymentfee.com provides access to a specific transaction receipt (transaction ID 277) behind an x402 paywall. The broader lowpaymentfee.com platform advertises a suite of pay-per-request APIs spanning data & analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance & Web3 data (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints are priced at $0.02 per request, settled in USDC on the Base network via the x402 protocol.
The specific endpoint probed (/api/v1/transactions/277/receipt) returns a valid x402 challenge with a maxAmountRequired of 20,000 base units of USDC (0x8335…2913 on Base). Since USDC uses 6 decimals, this equals $0.02 per call. Payment is made via the x402 "exact" scheme to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3, with a 300-second timeout. The endpoint accepts POST requests and returns application/json.
Documentation is extremely sparse — the /docs, /pricing, /api, and /README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI spec, no request/response schema documentation, and no examples of what the receipt payload actually contains. The platform's landing page lists many API paths but provides no detail on request parameters or response formats for any of them. Use with caution until better documentation is available.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 277 via a single paid API call
- —Programmatic access to paid data endpoints without API key management
- —Agent-driven micropayment workflows using x402 on Base
Fit
Best for
- —Developers experimenting with x402 payment protocol integrations
- —Agents that need to make small per-call payments in USDC on Base
- —Use cases requiring keyless, pay-as-you-go API access
Not for
- —Production workloads requiring documented request/response schemas
- —Users who need free or subscription-based API access
- —High-volume batch processing where $0.02/request adds up quickly
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/277/receipt
# Returns 402 with x402 challenge; include X-PAYMENT header with signed USDC payment to complete the request.Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but there is zero documentation on request parameters, response schema, or what the receipt actually contains. The /docs and other pages are empty beyond a wallet connect prompt. No OpenAPI spec exists. This is effectively a stub listing.
Warnings
- —No documentation available — /docs, /pricing, /api, and /README pages all show only 'Connect wallet' with no content
- —No OpenAPI or schema definition for request or response payloads
- —Unknown what data the transaction receipt actually returns
- —The endpoint is for a specific transaction ID (277); unclear if other transaction IDs are available or how they are discovered
- —The broader platform lists many API paths but none have documented schemas or examples
Citations
- —All endpoints priced at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —x402 challenge returns maxAmountRequired of 20000 base units of USDC (asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Basehttps://lowpaymentfee.com/api/v1/transactions/277/receipt
- —Platform lists APIs for analytics, AI/ML, finance/Web3, and infrastructure utilitieshttps://lowpaymentfee.com
- —Documentation pages (/docs, /pricing, /api, /README) contain only 'Connect wallet' prompthttps://lowpaymentfee.com/docs