x402-gated Stripe invoice endpoint on Base, paying $0.02 in USDC per request.
What it does
This endpoint at lowpaymentfee.com provides access to a Stripe invoice resource (invoice ID 121) behind an x402 paywall. The provider operates a suite of pay-per-request APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities, all gated via the x402 protocol on the Base network. Each call costs $0.02 in USDC (USD Coin) with no API keys, no rate limits, and no subscriptions required.
The specific endpoint `/api/v1/stripe/invoices/121` is labeled "Premium API Access" in the x402 challenge. It accepts HTTP POST requests and returns application/json. The x402 challenge advertises a maxAmountRequired of 20,000 base units of USDC (0x8335… on Base), which equals $0.02 given USDC's 6 decimals. Payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout.
Documentation is extremely sparse — the /docs, /pricing, /api, and /README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI spec, no request/response schema documentation, and no examples of what the invoice endpoint actually returns. The provider's landing page lists many other endpoints across categories (analytics, AI, finance, utilities) all at the same $0.02 price point, but none have documented schemas. The exact purpose and response format of this particular Stripe invoices endpoint is unclear from available materials.
Capabilities
Use cases
- —Retrieving Stripe invoice data via a crypto-gated pay-per-request model
- —Demonstrating x402 protocol payment flows on Base network
- —Accessing premium API resources without API keys or subscriptions
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents that can settle USDC payments on Base
- —Use cases needing keyless, pay-per-call API access
Not for
- —Production workloads requiring documented request/response schemas
- —Users who need free or fiat-only payment options
- —High-volume batch processing where per-request costs add up
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/stripe/invoices/121 \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge with clear pricing ($0.02 USDC on Base). However, there is no OpenAPI spec, no documented request/response schema, no examples, and the docs/pricing/README pages are all empty beyond a wallet connect prompt. The actual purpose and output of the Stripe invoices endpoint is undocumented.
Warnings
- —No OpenAPI or schema documentation available for this endpoint
- —All documentation pages (/docs, /pricing, /api, /README) render only 'Connect wallet' with no content
- —The exact purpose and response format of /api/v1/stripe/invoices/121 is unknown
- —No request body schema or example responses are documented anywhere
Citations
- —The x402 challenge advertises maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/stripe/invoices/121
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/stripe/invoices/121
- —All APIs are priced at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —The endpoint is described as 'Premium API Access' in the x402 challengehttps://lowpaymentfee.com/api/v1/stripe/invoices/121