Pay-per-call Stripe invoice endpoint on Base via x402, settling in USDC at $0.02/request.
What it does
This endpoint at lowpaymentfee.com provides access to a Stripe invoices resource via the x402 payment protocol. The specific path `/api/v1/stripe/invoices/10` suggests retrieval or creation of a Stripe invoice (likely invoice ID 10). Payment is settled on the Base network using USDC (contract 0x8335…2913) with a maximum cost of 20,000 base units, which equals $0.02 per request (USDC uses 6 decimals). The endpoint accepts POST requests and returns application/json.
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/crypto data feeds, and infrastructure utilities — all priced at $0.02 per request with no API keys, no rate limits, and no commitments. Each endpoint uses the x402 protocol on Base, meaning callers attach an X-PAYMENT header with a signed USDC payment to authenticate and pay in a single step.
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 usage examples available from the crawled content. The endpoint is confirmed live (returns a proper 402 challenge), but the actual behavior and response format of the Stripe invoices endpoint remain undocumented.
Capabilities
Use cases
- —Programmatically retrieving or creating Stripe invoices via a pay-per-call model without needing API keys
- —Integrating invoice data into agent workflows that can settle payments on Base in USDC
- —Testing x402 payment protocol integrations with a low-cost endpoint
Fit
Best for
- —Developers experimenting with x402 payment-gated APIs
- —Agents that need Stripe invoice access without managing API credentials
- —Low-volume, pay-as-you-go invoice operations
Not for
- —High-volume Stripe integrations where direct Stripe API access is more cost-effective
- —Users who need detailed documentation or guaranteed SLAs
- —Non-crypto users who cannot settle payments in USDC on Base
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/stripe/invoices/10 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <signed-x402-payment-header>"Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge, confirming it exists and accepts payments. However, there is no OpenAPI spec, no request/response schema, no documentation beyond a wallet-connect prompt, and no examples. The actual functionality of the Stripe invoices endpoint is unclear — it could be a demo or placeholder. This is effectively a stub listing.
Warnings
- —No documentation available — docs, API, pricing, and README pages all show only 'Connect wallet'
- —No OpenAPI or schema definition for request or response payloads
- —Unclear what the Stripe invoices endpoint actually returns or requires as input
- —The endpoint path includes a hardcoded ID (/invoices/10) which may indicate a demo or limited resource
- —No evidence of rate limits, SLAs, or uptime guarantees
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units in USDC on Base networkhttps://lowpaymentfee.com/api/v1/stripe/invoices/10
- —All APIs on the platform are priced at $0.02 per request with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/stripe/invoices/10
- —The platform offers APIs across data analytics, AI/ML, finance/crypto, and infrastructure categorieshttps://lowpaymentfee.com