x402-gated transaction receipt endpoint on Base, paying $0.02 in USDC per request.
What it does
This endpoint at lowpaymentfee.com provides access to a transaction receipt (resource ID 275) behind an x402 paywall. The site advertises itself as a platform hosting multiple pay-per-request API categories including Data & Analytics, AI & Machine Learning, Finance & Web3, and Infrastructure utilities — all priced at $0.02 per request, settled in USDC on the Base network.
The specific endpoint `/api/v1/transactions/275/receipt` returns a JSON response upon payment. The x402 challenge confirms it accepts an "exact" payment scheme on Base, requiring up to 20,000 base units of USDC (0x8335…2913), which equals $0.02 given USDC's 6 decimals. Payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout. No API keys or rate limits are advertised; access is granted purely via the x402 payment header.
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 beyond the x402 challenge's outputSchema stub, and no explanation of what the receipt data actually contains. The endpoint is live (402 challenge confirmed), but the lack of documentation makes it difficult to assess the actual utility of the returned data.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction ID 275 via micropayment
- —Demonstrating x402 payment protocol integration on Base
- —Agent-driven pay-per-request data retrieval without API key management
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents that need keyless, pay-per-call API access on Base
- —Projects exploring USDC micropayment-gated endpoints
Not for
- —Production use cases requiring documented response schemas and SLAs
- —Bulk data retrieval where per-request pricing is inefficient
- —Users without a Base-compatible USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/275/receipt \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge with clear pricing ($0.02 USDC on Base). However, documentation is essentially nonexistent — all doc pages show only 'Connect wallet'. There is no OpenAPI spec, no response schema, no example payloads, and no description of what the receipt data actually contains. The listing is effectively a stub.
Warnings
- —No documentation available — /docs, /api, /pricing, and /README pages all render only 'Connect wallet'
- —No OpenAPI or response schema provided; the actual content of the receipt is unknown
- —The endpoint path references a specific transaction ID (275); unclear if this is parameterized or a single fixed resource
- —The broader site advertises many API categories but none have documented schemas or examples
Citations
- —The endpoint returns HTTP 402 with an x402 challenge requiring 20,000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/transactions/275/receipt
- —All APIs on the site are priced at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset address is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/transactions/275/receipt
- —Documentation pages (/docs, /api, /pricing, /README) render only 'Connect wallet' with no further contenthttps://lowpaymentfee.com/docs