x402-gated Stripe invoice endpoint on Base, paying per-call in USDC.
What it does
This endpoint at lowpaymentfee.com exposes a specific Stripe invoice resource (`/api/v1/stripe/invoices/119`) behind an x402 paywall. The provider operates a broader platform offering dozens of pay-per-call APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services — all settled on the Base network using USDC via the x402 protocol.
The x402 challenge for this particular endpoint advertises a maximum cost of 20,000 base units of USDC (0.02 USD per request), consistent with the site-wide $0.02/request pricing shown on the landing page. Payment is made to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` using the USDC contract on Base (`0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`). The endpoint accepts POST requests and returns `application/json`.
However, the specific functionality of this endpoint — retrieving or interacting with Stripe invoice #119 — is not documented anywhere in the crawled material. The landing page lists many API categories (analytics, AI, finance, infrastructure) but does not mention Stripe invoice endpoints. No OpenAPI spec, request/response schemas, or usage examples were found. The docs, API, pricing, and README pages all rendered only a "Connect wallet" prompt with no substantive content. As a result, the actual behavior and response format of this endpoint remain unclear.
Capabilities
Use cases
- —Programmatically retrieving or interacting with a specific Stripe invoice via a crypto-settled paywall
- —Demonstrating x402 payment flows for agent-to-agent commerce
- —Integrating pay-per-call invoice access into automated billing workflows
Fit
Best for
- —Developers experimenting with x402 payment protocol on Base
- —Agents needing per-call access to invoice data without API keys
- —Projects requiring USDC-settled micropayment gating
Not for
- —Users needing well-documented, production-grade Stripe integrations
- —Anyone requiring bulk invoice management or Stripe dashboard features
- —Use cases needing free or subscription-based access
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/stripe/invoices/119 \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live (402 challenge captured) and pricing is clear ($0.02 USDC on Base), but there is no documentation, no OpenAPI schema, no request/response examples, and the specific purpose of a 'Stripe invoice #119' endpoint is unexplained. Docs pages returned only wallet-connect prompts. This is effectively a stub listing.
Warnings
- —No documentation available — docs, API, pricing, and README pages all render only a 'Connect wallet' prompt with no content
- —The specific endpoint /api/v1/stripe/invoices/119 is not listed among the provider's advertised APIs on the landing page
- —No request or response schema is available; actual behavior is unknown
- —Purpose of exposing a single Stripe invoice (ID 119) behind a paywall is unclear
Citations
- —The x402 challenge advertises maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/stripe/invoices/119
- —Site-wide pricing is $0.02 per request with no API keys, no rate limitshttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/stripe/invoices/119
- —The provider lists APIs across data/analytics, AI/ML, finance/web3, and infrastructure categorieshttps://lowpaymentfee.com