x402-gated transaction receipt endpoint on Base, paid per-call in USDC.
What it does
This endpoint at lowpaymentfee.com provides a transaction receipt resource (transaction ID 254) behind an x402 paywall. The provider operates a broader platform offering multiple API categories — data & analytics, AI/ML inference (sentiment, summarization, classification, embeddings), finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation) — all gated via the x402 protocol on the Base network with USDC payments.
The specific endpoint `/api/v1/transactions/254/receipt` accepts POST requests and returns JSON. The x402 challenge advertises a maximum cost of 20,000 base units of USDC (asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913, which uses 6 decimals), equating to $0.02 per request. The platform's landing page confirms uniform $0.02/request pricing across all endpoints. No API keys or rate limits are required; payment is handled entirely through the x402 payment header. The payment is settled on the Base L2 network to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3.
Documentation is extremely sparse — the /docs, /api, /pricing, 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 endpoint is confirmed live (returns 402 with a valid x402 challenge), but the lack of documentation makes it difficult to know what data the receipt contains or what POST body (if any) is expected.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 254 via a micropayment
- —Programmatic access to paid API resources without API key management
- —Agent-driven workflows that settle per-call costs in USDC on Base
Fit
Best for
- —Developers or agents needing x402-compatible paid endpoints on Base
- —Use cases requiring keyless, pay-per-request API access
- —Exploring x402 protocol integration patterns
Not for
- —Users who need detailed API documentation or OpenAPI specs before integrating
- —Bulk or high-volume use cases where per-request pricing may add up
- —Anyone needing endpoints beyond this single transaction receipt without further exploration
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/254/receipt \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is confirmed live with a valid x402 challenge and clear pricing ($0.02/request in USDC on Base). However, there is no OpenAPI spec, no documented request/response schema, no examples, and the docs pages are empty. The specific purpose of this receipt endpoint is unclear beyond its URL path.
Warnings
- —No API documentation available — /docs, /api, /pricing, and /README pages all show only 'Connect wallet' with no content.
- —No OpenAPI or schema definition for request body or response payload.
- —The specific data returned by the /transactions/254/receipt endpoint is unknown — the endpoint path suggests a single hardcoded transaction ID, which may indicate a demo or placeholder.
- —The broader platform advertises many endpoint categories (AI, analytics, finance, utilities) but none have documented schemas.
Citations
- —The x402 challenge returns maxAmountRequired of 20000 base units of USDC (asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Base networkhttps://lowpaymentfee.com/api/v1/transactions/254/receipt
- —The platform advertises $0.02/request uniform pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —The platform lists API categories including Data & Analytics, AI & Machine Learning, Finance & Web3, and Infrastructurehttps://lowpaymentfee.com
- —Documentation pages (/docs, /api, /pricing, /README) render only a 'Connect wallet' prompthttps://lowpaymentfee.com/docs