x402-gated Stripe invoice endpoint on Base, paying $0.02 per request in USDC.
What it does
This endpoint at lowpaymentfee.com provides access to a Stripe invoice resource (invoice ID 159) behind an x402 payment wall. The endpoint accepts POST requests and returns application/json responses. Payment is settled on the Base network using USDC (contract 0x8335…2913) with a maximum amount of 20,000 base units, which equals $0.02 USD (USDC uses 6 decimals). No API keys or rate limits are required — callers simply attach an X-PAYMENT header with a valid x402 payment proof.
The broader lowpaymentfee.com platform advertises a suite of pay-per-call APIs spanning data analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance/Web3 data (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints are listed at $0.02 per request with no minimums or commitments. However, this specific listing is for the Stripe invoices endpoint at path /api/v1/stripe/invoices/159, whose exact response payload is not documented in the crawled material.
The x402 challenge was successfully captured (HTTP 402 with version 1 challenge), confirming the endpoint is live. Documentation on the site is extremely thin — the /docs, /api, /pricing, and /README pages all returned only a "Connect wallet" prompt with no substantive content. There is no OpenAPI spec, no request/response schema documentation, and no usage examples available from the crawl.
Capabilities
Use cases
- —Retrieving Stripe invoice data programmatically via a single micropayment
- —Agent-driven invoice lookups without pre-registration or API keys
- —Integrating pay-per-use invoice access into automated financial workflows
Fit
Best for
- —Agents needing one-off Stripe invoice data without subscription overhead
- —Developers experimenting with x402 payment-gated APIs on Base
- —Low-volume, on-demand invoice retrieval
Not for
- —High-volume bulk invoice processing (no documented batch support)
- —Users who need detailed API documentation or guaranteed SLAs
- —Non-crypto users who cannot settle payments on the Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/stripe/invoices/159 \
-H "X-PAYMENT: <x402_payment_proof>" \
-H "Content-Type: application/json"Endpoint
Quality
The x402 challenge is live and confirms pricing and network details, but there is zero documentation on request/response schemas, no OpenAPI spec, and all doc pages return only a wallet-connect prompt. The specific purpose of the /stripe/invoices/159 endpoint is unclear beyond its name.
Warnings
- —No API documentation available — /docs, /api, /pricing, and /README pages all return only 'Connect wallet' with no content.
- —No OpenAPI or request/response schema provided; the exact payload structure is unknown.
- —The endpoint path references a specific invoice ID (159), which may be a demo or placeholder resource rather than a general-purpose API.
- —The broader platform lists many endpoint categories but none could be verified beyond the landing page descriptions.
Citations
- —The x402 challenge returns maxAmountRequired of 20000 base units in USDC on Base networkhttps://lowpaymentfee.com/api/v1/stripe/invoices/159
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/stripe/invoices/159
- —All endpoints listed at $0.02 per request with no API keys, no rate limits, and no minimumshttps://lowpaymentfee.com
- —Platform advertises APIs across data/analytics, AI/ML, finance/Web3, and infrastructure categorieshttps://lowpaymentfee.com