Pay-per-call transaction receipt endpoint on Base via x402, settling in USDC at $0.02/request.
What it does
This x402-enabled endpoint at lowpaymentfee.com provides a transaction receipt retrieval API. When called via POST at `/api/v1/transactions/334/receipt`, it returns a JSON receipt for the specified transaction. Payment is handled inline via the x402 protocol: the endpoint returns a 402 challenge requiring a USDC payment on the Base network before serving the response.
The specific endpoint probed charges a maximum of 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 per request. The broader lowpaymentfee.com platform advertises a uniform $0.02/request pricing across a wide catalog of endpoints spanning data analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance/crypto market data, and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints are x402-gated with no API keys, no rate limits, and no minimum commitments.
Documentation is extremely sparse — the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI spec, no request/response schema documentation, and no example payloads available. The endpoint is live (402 challenge confirmed), but the actual response format and data content behind the paywall are unknown.
Capabilities
Use cases
- —Retrieving transaction receipts programmatically with per-call USDC payment
- —Agent-driven workflows that need on-demand financial transaction data without pre-registration
- —Demonstrating x402 payment protocol integration for pay-per-use APIs
Fit
Best for
- —Developers experimenting with x402 protocol payments
- —Agents that need keyless, on-demand API access settled in USDC on Base
- —Low-volume, pay-as-you-go transaction data retrieval
Not for
- —Production workloads requiring documented request/response schemas
- —High-volume use cases where per-call crypto settlement overhead matters
- —Users who need detailed API documentation or SDKs before integrating
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/334/receipt
# Returns 402 with x402 challenge; attach X-PAYMENT header with signed USDC payment to receive the receipt.Endpoint
Quality
The endpoint is live and returns a valid x402 challenge with clear pricing, but documentation is essentially nonexistent — all doc pages show only 'Connect wallet'. No OpenAPI spec, no request/response schemas, no examples. The actual data returned behind the paywall is unknown, making this effectively a stub listing.
Warnings
- —No API documentation available — all doc/pricing/README pages render only 'Connect wallet'
- —No OpenAPI or schema definition found; request and response formats are unknown
- —The specific endpoint path includes a hardcoded transaction ID (334); unclear if this is parameterized or fixed
- —The broader platform advertises many endpoint categories (AI, finance, utils) but none could be verified beyond the 402 challenge
Citations
- —Endpoint returns 402 with x402 challenge requiring USDC payment on Base network, maxAmountRequired 20000 base unitshttps://lowpaymentfee.com/api/v1/transactions/334/receipt
- —Platform advertises $0.02/request uniform pricing with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/transactions/334/receipt
- —Docs, API, pricing, and README pages all show only 'Connect wallet' with no further contenthttps://lowpaymentfee.com/docs