x402-payable transaction receipt endpoint on Base, settling in USDC at $0.02 per request.
What it does
This endpoint at lowpaymentfee.com provides a "Premium API Access" resource for retrieving a transaction receipt (transaction ID 48) via the x402 payment protocol. It is part of a broader platform that offers a variety of pay-per-call APIs spanning data & analytics, AI/ML inference, finance & Web3 data, and infrastructure utilities — all priced at $0.02 per request and settled in USDC on the Base network.
The specific endpoint `/api/v1/transactions/48/receipt` accepts POST requests and returns `application/json`. Payment is handled via the x402 exact-payment scheme: the caller includes an `X-PAYMENT` header with a signed USDC payment of up to 20,000 base units (i.e., $0.02, since USDC uses 6 decimals) to the payee address `0x1A2B…85F3`. The asset contract is the canonical Base USDC at `0x8335…2913`. No API keys or rate limits are advertised; access is gated purely by micropayment.
Documentation on the site is extremely thin — the /docs, /pricing, /api, and /README pages all render only a "Connect wallet" prompt with no additional technical detail. There is no OpenAPI spec, no request/response schema beyond the x402 challenge's `outputSchema` stub, and no example payloads. The platform appears to be a demonstration or early-stage deployment of x402-based API monetization. The endpoint is confirmed live (returns a proper 402 challenge).
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 48 via micropayment
- —Demonstrating x402 protocol integration for pay-per-call APIs
- —Agent-driven API consumption without API key management
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents that can sign USDC payments on Base for per-call access
- —Use cases requiring keyless, pay-as-you-go API access
Not for
- —Production workloads needing documented request/response schemas
- —Users without a Base-network USDC wallet
- —High-volume batch processing where per-call payment overhead is impractical
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/48/receipt
# Returns 402 with x402 challenge. Include a signed X-PAYMENT header
# paying 20000 base-units USDC ($0.02) on Base to complete the request.Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but there is no OpenAPI spec, no documented request body schema, no example responses, and the docs pages are empty stubs. The specific purpose of this particular receipt endpoint is unclear beyond its URL path. Effectively a stub listing.
Warnings
- —No OpenAPI or schema documentation available — request and response formats are unknown
- —All documentation pages (/docs, /pricing, /api, /README) render only 'Connect wallet' with no content
- —The endpoint path suggests a single hardcoded transaction ID (48); unclear if this generalizes
- —Platform appears to be early-stage or a demo; reliability and longevity are uncertain
Citations
- —Endpoint returns a 402 challenge with x402Version 1, exact scheme, Base network, USDC asset at 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/transactions/48/receipt
- —maxAmountRequired is 20000 base units USDC (6 decimals) = $0.02https://lowpaymentfee.com/api/v1/transactions/48/receipt
- —Platform advertises $0.02/request pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —Platform lists APIs across Data & Analytics, AI & ML, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com