x402-gated Stripe invoice endpoint on Base, paid per-call in USDC.
What it does
This endpoint at lowpaymentfee.com exposes a specific Stripe invoice resource (`/api/v1/stripe/invoices/138`) behind an x402 paywall. It is part of a broader platform that offers dozens of pay-per-request API endpoints spanning data analytics, AI/ML inference, finance/Web3 data, and utility services — all settled on the Base network using USDC.
The x402 challenge confirms the endpoint is live and accepts POST requests. The price is 20,000 base units of USDC (6 decimals), which equals $0.02 per request. Payment is made to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` on Base using the exact payment scheme. The maximum timeout is 300 seconds. The response MIME type is `application/json`.
The specific functionality of this particular endpoint — retrieving or interacting with Stripe invoice #138 — is not well-documented. The platform's landing page lists many API categories (analytics, AI, finance, infrastructure) but does not include this Stripe invoices path among them. No OpenAPI schema, request/response examples, or detailed documentation were found in the crawl. The docs, API, pricing, and README pages all rendered only a "Connect wallet" prompt with no substantive content. This makes it difficult to determine exactly what data this endpoint returns or what input it expects beyond a POST request.
Capabilities
Use cases
- —Retrieving Stripe invoice data via a single paid API call
- —Programmatic access to invoice #138 without API key management
- —Agent-driven invoice lookups settled in USDC on Base
Fit
Best for
- —Agents or services that need on-demand invoice data without subscription commitments
- —Developers wanting keyless, pay-per-use API access on Base
- —Crypto-native workflows that settle in USDC
Not for
- —Users needing bulk invoice retrieval across many invoice IDs
- —Anyone requiring detailed API documentation or schema guarantees before integration
- —Non-crypto users who cannot pay in USDC on Base
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/stripe/invoices/138 \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02/request in USDC on Base). However, there is no OpenAPI schema, no request/response examples, and no documentation explaining what this specific Stripe invoice endpoint does. The docs pages returned only wallet-connect prompts. The endpoint path itself (invoices/138) suggests a hardcoded resource rather than a general-purpose API, which is unusual.
Warnings
- —No documentation available — docs, API, pricing, and README pages all show only a 'Connect wallet' prompt with no content
- —No OpenAPI or input/output schema provided for this endpoint
- —The endpoint path references a specific invoice ID (138), suggesting it may be a single fixed resource rather than a parameterized API
- —The Stripe invoices path is not listed among the platform's advertised API categories on the landing page
- —Actual response content and structure are unknown
Citations
- —The endpoint returns a 402 challenge with x402Version 1, accepting USDC on Base with maxAmountRequired of 20000 (=$0.02)https://lowpaymentfee.com/api/v1/stripe/invoices/138
- —The platform advertises $0.02/request pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/stripe/invoices/138
- —Docs, API, pricing, and README pages render only a 'Connect wallet' prompthttps://lowpaymentfee.com/docs