x402-gated Stripe invoice endpoint on Base, paying $0.02 in USDC per request.
What it does
This endpoint at lowpaymentfee.com provides premium API access to a Stripe invoice resource (invoice #176) behind an x402 paywall. It is part of a broader platform offering pay-per-request APIs across data analytics, AI/ML inference, finance/Web3, and infrastructure utility categories — all priced at $0.02 per call, settled in USDC on the Base network.
The specific endpoint `/api/v1/stripe/invoices/176` accepts POST requests and returns `application/json`. Payment is handled via the x402 protocol: callers must include an `X-PAYMENT` header containing a valid payment proof for 20,000 base units of USDC (0.02 USD, since USDC uses 6 decimals) sent to the designated payTo address on Base. The payment scheme is "exact" with a 300-second timeout window. No API keys or rate limits are advertised — access is purely gated by micropayment.
Documentation on the site is extremely sparse. The docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI spec, no request/response schema documentation, and no explanation of what data the Stripe invoices endpoint actually returns. The endpoint is confirmed live (402 challenge captured), but the lack of documentation makes it difficult to determine the exact functionality or expected request body format.
Capabilities
Use cases
- —Retrieving Stripe invoice data via a single micropayment without needing an API key
- —Programmatic access to invoice information for agents that can settle x402 payments
- —Demonstrating x402 protocol integration for pay-per-request API monetization
Fit
Best for
- —Agents or bots that can autonomously settle x402 USDC payments on Base
- —Developers exploring x402 protocol-based API monetization patterns
- —Low-volume, on-demand invoice data retrieval without subscription commitments
Not for
- —Users who need detailed API documentation or request/response schemas before integrating
- —High-volume invoice processing where per-request micropayments become inefficient
- —Anyone without a Base-compatible USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/stripe/invoices/176 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-proof>"Endpoint
Quality
The endpoint is confirmed live via a valid 402 challenge, and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI spec, no request/response schema, and all documentation pages are empty beyond a wallet-connect prompt. The actual functionality of the Stripe invoices endpoint is unexplained, making this effectively a stub listing.
Warnings
- —No API documentation available — docs, API, pricing, and README pages all show only 'Connect wallet'
- —No OpenAPI or JSON schema describing request body or response format
- —Unclear what data the /api/v1/stripe/invoices/176 endpoint actually returns
- —The endpoint path references a specific invoice ID (176), which may indicate a demo or test resource rather than a general-purpose API
Citations
- —The endpoint returns a 402 challenge requiring 20,000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/stripe/invoices/176
- —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/176
- —The platform offers APIs across Data & Analytics, AI & Machine Learning, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com