x402-gated Stripe invoice endpoint on Base, paid per-call in USDC.
What it does
This endpoint at lowpaymentfee.com exposes a Stripe invoice resource (`/api/v1/stripe/invoices/83`) behind an x402 paywall. When called without payment, it returns a 402 challenge requesting USDC on the Base network. The challenge specifies a maximum amount of 20,000 base units of USDC (0.02 USD, since USDC uses 6 decimals), consistent with the site-wide $0.02/request pricing advertised on the landing page.
The broader lowpaymentfee.com platform advertises multiple API categories — data & analytics, AI/ML inference, finance/Web3, and infrastructure utilities — all at the same $0.02 per request price point. However, this specific listing is for the Stripe invoices endpoint (resource ID 83). The x402 challenge indicates the payment scheme is "exact" (one-shot per call), the asset is USDC at contract `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913` on Base, and the timeout is 300 seconds.
Documentation is extremely sparse: the /docs, /api, /pricing, and /README pages all returned only a "Connect wallet" prompt with no substantive content. There is no OpenAPI spec, no request/response schema, and no description of what the invoice endpoint actually returns. The endpoint is live (402 challenge confirmed), but without documentation it is unclear what data or functionality the response provides beyond the generic label "Premium API Access."
Capabilities
Use cases
- —Retrieving Stripe invoice data via a pay-per-call model without API keys
- —Agent-initiated invoice lookups settled in USDC on Base
- —Programmatic access to invoice records with micropayment gating
Fit
Best for
- —Agents or scripts that need one-off invoice data without subscription overhead
- —Developers experimenting with x402 payment flows
- —Use cases where no-API-key, pay-per-request access is preferred
Not for
- —Bulk invoice processing requiring thousands of calls (no documented rate limits but cost adds up)
- —Users who need detailed API documentation or guaranteed SLAs
- —Non-crypto users who cannot pay in USDC on Base
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/stripe/invoices/83 \
-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 effectively nonexistent — every doc page returns only 'Connect wallet'. There is no OpenAPI spec, no request/response schema, and no explanation of what the endpoint actually returns. The listing is a stub with confirmed liveness.
Warnings
- —No documentation available — /docs, /api, /pricing, and /README all return only 'Connect wallet'
- —No OpenAPI or output schema provided; response format is unknown
- —The specific resource '/api/v1/stripe/invoices/83' is not listed on the landing page's API catalog, raising questions about its intended use
- —Purpose of 'Premium API Access' label is unclear without further context
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/stripe/invoices/83
- —Site-wide pricing is $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/83
- —Documentation pages (/docs, /api, /pricing, /README) contain only 'Connect wallet' with no substantive contenthttps://lowpaymentfee.com/docs