x402-gated transaction receipt endpoint on Base, paying $0.02 in USDC per request.
What it does
This endpoint at lowpaymentfee.com provides a transaction receipt resource (transaction ID 201) behind an x402 paywall. It is part of a broader platform that offers a variety of pay-per-request APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all priced at $0.02 per call, settled in USDC on the Base network.
The specific endpoint `/api/v1/transactions/201/receipt` accepts POST requests and returns JSON. The x402 challenge advertises 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 x402 exact scheme with a 300-second timeout. No API keys or rate limits are advertised; access is granted purely through the x402 payment header.
Documentation on the site is extremely sparse — the docs, API, pricing, 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 usage examples. The endpoint is confirmed live (returns HTTP 402 with a valid x402 challenge), but the actual functionality behind the paywall and the structure of the response are unknown beyond the description "Premium API Access" and the mime type application/json.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 201 via a single micropayment
- —Demonstrating x402 protocol integration for pay-per-request APIs
- —Agent-driven access to paid JSON endpoints without API key management
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents that need keyless, pay-per-call API access on Base
- —Users who want to avoid subscription commitments for occasional API calls
Not for
- —Production workloads requiring documented request/response schemas
- —Users who need bulk or high-volume access with negotiated pricing
- —Anyone without a Base-compatible USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/201/receipt \
-H "X-PAYMENT: <x402-payment-header>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is confirmed live with a valid x402 challenge, but there is no documentation, no OpenAPI spec, no request/response examples, and the docs pages are empty stubs. The actual functionality behind the paywall is unclear beyond the generic label 'Premium API Access'. This is effectively a stub listing.
Warnings
- —No OpenAPI spec or schema documentation available
- —All documentation pages (docs, API, pricing, README) render only 'Connect wallet' with no content
- —The actual response payload structure is unknown — no examples or schema provided
- —The specific purpose of 'transaction 201 receipt' is undocumented
- —The broader platform lists many endpoints but none have documented schemas
Citations
- —The endpoint returns HTTP 402 with x402 version 1 challenge advertising USDC on Basehttps://lowpaymentfee.com/api/v1/transactions/201/receipt
- —maxAmountRequired is 20000 base units of USDC (USD Coin, 6 decimals) = $0.02https://lowpaymentfee.com/api/v1/transactions/201/receipt
- —The platform advertises $0.02/request pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —Documentation pages render only 'Connect wallet' with no substantive contenthttps://lowpaymentfee.com/docs