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 196) 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/196/receipt) returned a valid x402 challenge with a maxAmountRequired of 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimals. Payment is made via the "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 substantive content. There is no OpenAPI spec, no request/response schema documentation, and no examples of what the receipt payload actually contains. The platform's value proposition centers on simplicity (no API keys, no rate limits, instant access), but without documentation it is difficult to know what data any of these endpoints actually return.
Capabilities
Use cases
- —Retrieving transaction receipt data for transaction ID 196 via a single paid request
- —Programmatic access to paid API endpoints without API key management
- —Agent-driven micropayment workflows using x402 on Base
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents that need keyless, pay-per-call API access on Base
- —Use cases requiring low-cost ($0.02) per-request pricing with no commitments
Not for
- —Production workloads requiring documented request/response schemas
- —Users who need free or subscription-based API access
- —Applications requiring high-throughput with predictable bulk pricing
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/196/receipt
# Returns 402 with x402 challenge; include X-PAYMENT header with valid USDC payment to access the receipt.Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but documentation is effectively nonexistent — all doc pages show only 'Connect wallet'. There is no OpenAPI spec, no request/response schema, and no examples. The specific endpoint path (transactions/196/receipt) is a single hardcoded resource ID with no explanation of what it returns. The broader platform lists many endpoints but none are documented.
Warnings
- —No documentation available — /docs, /pricing, /api, and /README all render only 'Connect wallet'
- —No OpenAPI or schema definition found for any endpoint
- —The probed endpoint references a specific transaction ID (196); unclear if this is a demo or a real resource
- —No response schema or example output available to verify what data is actually returned
- —Platform lists many API categories (AI, finance, analytics, etc.) but none have documented behavior
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/transactions/196/receipt
- —All endpoints are priced at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —The platform advertises APIs across data/analytics, AI/ML, finance/Web3, and infrastructure categorieshttps://lowpaymentfee.com
- —Documentation pages (/docs, /pricing, /api, /README) render only 'Connect wallet' with no contenthttps://lowpaymentfee.com/docs