x402-gated Stripe invoice endpoint on Base, pay-per-call with USDC.
What it does
This endpoint at lowpaymentfee.com exposes a Stripe invoice resource (`/api/v1/stripe/invoices/88`) behind an x402 payment challenge. The endpoint accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) with a maximum cost of 0.02 USDC per request (20000 base units at 6 decimals). The x402 challenge version is 1, using the "exact" payment scheme, with a 300-second timeout.
The provider, lowpaymentfee.com, offers a broader catalog of pay-per-call APIs spanning data & analytics, AI/ML (sentiment analysis, summarization, classification, embeddings), finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation) — all priced at $0.02 per request with no API keys, no rate limits, and no commitments. However, this specific listing is for the Stripe invoices endpoint (resource ID 88), whose exact response payload and business logic are not documented in the crawled material.
The endpoint is live: the probe received a proper HTTP 402 with a well-formed x402 challenge. Documentation pages (/docs, /pricing, /api, /README) all returned only a "Connect wallet" prompt with no substantive content, so the actual request/response schema for this invoice endpoint is unknown beyond what the x402 challenge's outputSchema indicates (HTTP POST, discoverable).
Capabilities
Use cases
- —Retrieving or interacting with a Stripe invoice programmatically via crypto micropayment
- —Agent-driven invoice access without traditional API key provisioning
- —Paying per-request for financial document retrieval on Base L2
Fit
Best for
- —Agents or services that need keyless, pay-per-call access to invoice data
- —Developers building on Base who want USDC-settled API calls
- —Workflows requiring no upfront subscription or rate-limit negotiation
Not for
- —Users needing detailed API documentation or guaranteed SLA before integrating
- —High-volume invoice processing where per-call pricing may add up
- —Non-crypto users who cannot settle payments on the Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/stripe/invoices/88 \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live with a valid x402 402 challenge, but there is no documentation, no request/response schema, and no explanation of what the Stripe invoices endpoint actually returns. All doc pages render only 'Connect wallet' with no content. The listing is essentially a stub with confirmed liveness and pricing.
Warnings
- —No documentation available — all doc pages (/docs, /pricing, /api, /README) return only 'Connect wallet' with no content.
- —Request and response schemas for this specific endpoint are completely unknown.
- —The purpose and behavior of '/api/v1/stripe/invoices/88' (a hardcoded invoice ID) is unclear — it may be a demo or placeholder resource.
- —The broader catalog lists many endpoints but none have documented schemas or examples.
Citations
- —Endpoint returns HTTP 402 with x402 v1 challenge, exact scheme, Base network, USDC asset at 20000 base unitshttps://lowpaymentfee.com/api/v1/stripe/invoices/88
- —Provider advertises $0.02/request pricing with no API keys, no rate limits, instant access on Base networkhttps://lowpaymentfee.com
- —USDC contract address on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/stripe/invoices/88
- —Documentation pages return only 'Connect wallet' with no substantive contenthttps://lowpaymentfee.com/docs