x402-gated Stripe invoice endpoint on Base, paying $0.02 per request in USDC.
What it does
This endpoint at lowpaymentfee.com provides premium API access to a Stripe invoice resource via the x402 payment protocol. The specific path `/api/v1/stripe/invoices/111` suggests it returns or processes a Stripe invoice identified by ID 111. 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 provider's landing page advertises a broad suite of pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all priced at $0.02 per request with no API keys, no rate limits, and no commitments. However, the specific endpoint being listed here is scoped to the Stripe invoices path. Documentation pages (docs, pricing, README) returned only a wallet-connect prompt with no substantive content, so the exact request/response schema for this endpoint is unknown.
The x402 challenge is live and well-formed (version 1, scheme "exact", POST method, discoverable). The payTo address is 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3. Timeout is 300 seconds. No OpenAPI spec, no example payloads, and no detailed documentation were found, so the actual behavior behind the paywall is unverified.
Capabilities
Use cases
- —Retrieving or processing a Stripe invoice via a crypto-settled paywall
- —Demonstrating x402 payment protocol integration with Stripe billing data
- —Agent-driven invoice lookup without traditional API key authentication
Fit
Best for
- —Developers exploring x402 protocol with real endpoints
- —Agents needing keyless, pay-per-call access to invoice data
- —Projects settling API costs in USDC on Base L2
Not for
- —Bulk invoice processing requiring high throughput (no documented rate guarantees)
- —Users needing detailed API documentation or OpenAPI specs before integrating
- —Non-crypto workflows that require traditional auth and billing
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/stripe/invoices/111 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The x402 challenge is live and well-formed, confirming the endpoint exists and accepts payment. However, there is no OpenAPI spec, no request/response schema, and all documentation pages returned only a wallet-connect stub. The actual functionality behind the paywall is unverified, making this effectively a stub listing.
Warnings
- —No OpenAPI or schema documentation available — request and response formats are unknown
- —All doc/pricing/README pages returned only a wallet-connect prompt with no content
- —The specific behavior of /api/v1/stripe/invoices/111 is unverified behind the paywall
- —Provider site lists many diverse API categories but none have documented schemas
Citations
- —The x402 challenge returns maxAmountRequired of 20000 in USDC (6 decimals) on Base, equaling $0.02https://lowpaymentfee.com/api/v1/stripe/invoices/111
- —Provider advertises $0.02/request pricing 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/111
- —PayTo address is 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3https://lowpaymentfee.com/api/v1/stripe/invoices/111