x402-gated transaction receipt endpoint on Base, paid per-call in USDC.
What it does
This endpoint at lowpaymentfee.com provides access to a specific transaction receipt (transaction ID 276) behind an x402 paywall. The provider operates a broader platform offering multiple API categories — data & analytics, AI/ML inference, finance & Web3, and infrastructure utilities — all gated via the x402 protocol on the Base network, settled in USDC.
The specific endpoint `/api/v1/transactions/276/receipt` accepts POST requests and returns JSON. The x402 challenge advertises a maximum cost of 20,000 base units of USDC (0x8335… on Base), which equals $0.02 per request (USDC uses 6 decimals). The provider's landing page confirms a flat $0.02/request pricing model across all endpoints, with no API keys, no rate limits, and no minimum commitments required.
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 example payloads available. The endpoint is live (returns a valid x402 402 challenge), but without documentation it is unclear what request body the POST expects or what the receipt response contains. The broader platform lists 16 endpoints across four categories, but this specific endpoint (transactions/276/receipt) is not listed among them, suggesting it may be a demo or test resource.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 276 via a single micropayment
- —Demonstrating x402 protocol payment flows on Base
- —Agent-driven pay-per-call data retrieval without API key management
Fit
Best for
- —Developers experimenting with x402 protocol integrations
- —Agents that need keyless, pay-per-call API access on Base
- —Testing USDC micropayment workflows
Not for
- —Production use cases requiring documented request/response schemas
- —Bulk or high-volume transaction receipt retrieval (no batch endpoint documented)
- —Users who need traditional API-key-based authentication
Quick start
# Send a POST with x402 payment header to retrieve the receipt
curl -X POST https://lowpaymentfee.com/api/v1/transactions/276/receipt \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge with clear pricing ($0.02/request in USDC on Base). However, there is no OpenAPI spec, no request/response documentation, no examples, and the docs pages are empty. The specific endpoint (transactions/276/receipt) is not listed on the provider's own landing page, raising questions about its purpose and permanence.
Warnings
- —No OpenAPI or schema documentation available — request body format and response structure are unknown
- —The /docs, /pricing, /api, and /README pages contain no usable content (only 'Connect wallet')
- —This specific endpoint (/api/v1/transactions/276/receipt) is not listed among the provider's advertised APIs, suggesting it may be a test or demo resource
- —No information about what transaction 276 represents or whether other transaction IDs are accessible
Citations
- —The x402 challenge advertises maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/transactions/276/receipt
- —The provider lists 16 API endpoints across four categories at $0.02/request with no API keys, no rate limitshttps://lowpaymentfee.com
- —USDC asset address is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/transactions/276/receipt