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 `/api/v1/transactions/384/receipt`) behind an x402 paywall. The provider operates a broader platform offering multiple API categories — data & analytics, AI & machine learning, finance & Web3, and infrastructure utilities — all gated via the x402 protocol on the Base network, each priced at $0.02 per request in USDC.
The specific endpoint probed returns a 402 challenge requesting payment of 20,000 base units of USDC (0x8335…2913 on Base, 6 decimals), which equals $0.02. Payment is made via the x402 "exact" scheme to the specified payTo address. The endpoint accepts POST requests and returns `application/json`. No API keys or rate limits are advertised; access is granted purely through per-call micropayments.
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 endpoint is live (402 challenge confirmed), but without documentation it is unclear what data the receipt returns or what input parameters (if any) the POST body should contain.
Capabilities
Use cases
- —Retrieving transaction receipt data for transaction ID 384 via micropayment
- —Demonstrating x402 protocol integration for agent-purchasable endpoints
- —Building pay-per-use workflows that settle in USDC on Base
Fit
Best for
- —Developers experimenting with x402 micropayment protocol
- —Agents needing on-demand transaction receipts without API key management
- —Low-volume, pay-as-you-go API consumption on Base
Not for
- —Users needing well-documented APIs with clear request/response schemas
- —High-volume batch processing where per-call fees add up
- —Anyone requiring non-crypto payment methods
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/384/receipt
# Returns 402 with x402 challenge; attach X-PAYMENT header with signed USDC payment to access.Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge, confirming it is operational. However, documentation is effectively nonexistent — all doc pages show only 'Connect wallet'. There is no OpenAPI spec, no request/response schema, no examples, and no explanation of what the receipt endpoint actually returns. The listing is essentially a stub.
Warnings
- —No documentation available — /docs, /pricing, /api, and /README pages all render only 'Connect wallet' with no content.
- —No OpenAPI or schema definition found; request body format and response structure are unknown.
- —This appears to be a single hardcoded transaction ID (384); unclear if other transaction IDs are supported or what the broader use case is.
- —The broader platform advertises many endpoints (AI, analytics, finance, utils) but none have documented schemas or examples.
Citations
- —The endpoint returns a 402 challenge requesting 20,000 base units of USDC on Base (asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913), equaling $0.02.https://lowpaymentfee.com/api/v1/transactions/384/receipt
- —The platform advertises $0.02/request pricing with no API keys, no rate limits, and instant access on Base network.https://lowpaymentfee.com
- —The platform offers endpoints across Data & Analytics, AI & Machine Learning, Finance & Web3, and Infrastructure categories.https://lowpaymentfee.com
- —Documentation pages (/docs, /pricing, /api, /README) render only 'Connect wallet' with no substantive content.https://lowpaymentfee.com/docs