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/184`) 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 gated via the x402 protocol on the Base network and settled in USDC.
The specific endpoint listed here is labeled "Premium API Access" and costs up to 0.02 USDC per request (maxAmountRequired = 20000 base units of USDC with 6 decimals). It accepts HTTP POST, returns `application/json`, and requires no API keys or account registration. The x402 challenge directs payment to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` on Base, using the USDC contract at `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`.
Documentation 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, and no explanation of what data the `/stripe/invoices/184` endpoint actually returns. The endpoint is live (returns a valid 402 challenge), but without documentation it is unclear what payload to send or what response to expect beyond JSON.
Capabilities
Use cases
- —Retrieving Stripe invoice data via a single micropayment without needing an API key
- —Programmatic access to invoice #184 for agents that can settle x402 payments on Base
- —Demonstrating x402 protocol integration for pay-per-call billing
Fit
Best for
- —Agents or scripts that already support x402 payment flows on Base
- —Developers exploring x402 micropayment patterns with real endpoints
- —Use cases where keyless, per-call billing is preferred over subscriptions
Not for
- —Users who need detailed API documentation or request/response schemas before integrating
- —High-volume invoice retrieval where per-call costs would accumulate significantly
- —Anyone needing access to arbitrary Stripe invoices (this endpoint is scoped to invoice 184)
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/stripe/invoices/184 \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but documentation is essentially nonexistent—docs, API, pricing, and README pages all show only 'Connect wallet'. There is no OpenAPI spec, no request/response schema, and no explanation of what this specific Stripe invoice endpoint returns or what input it expects. The listing is effectively a stub.
Warnings
- —No documentation available—docs, API, pricing, and README pages render only 'Connect wallet'
- —No OpenAPI or request/response schema provided; input and output formats are unknown
- —Endpoint is scoped to a single Stripe invoice (ID 184); unclear what data it exposes or why
- —The broader platform lists many endpoints but none have documented schemas
Citations
- —The endpoint returns a valid x402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/stripe/invoices/184
- —The platform advertises $0.02 per request, no API keys, no rate limits, instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/stripe/invoices/184
- —Docs, API, pricing, and README pages show only 'Connect wallet' with no further contenthttps://lowpaymentfee.com/docs