x402-gated Stripe invoice endpoint on Base, paid per-call in USDC.
What it does
This endpoint at lowpaymentfee.com exposes a specific Stripe invoice resource (`/api/v1/stripe/invoices/19`) 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 settled on the Base network using USDC via the x402 protocol.
The x402 challenge for this particular endpoint advertises a maximum cost of 20,000 base units of USDC (0.02 USD) per request. Payment is made to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` on Base using the USDC contract `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`. The endpoint accepts POST requests and returns `application/json`. The payment scheme is "exact" with a 300-second timeout.
Documentation is extremely sparse. The crawled 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 description of what the Stripe invoice endpoint actually returns or what parameters it accepts. The endpoint title "Premium API Access" and the path suggest it may return or interact with a Stripe invoice object, but this is speculative. The broader site lists many API categories at $0.02/request with claims of no API keys, no rate limits, and instant access, but none of these claims can be verified from the available material.
Capabilities
Use cases
- —Retrieving Stripe invoice data via a single paid API call
- —Programmatic access to invoice information without traditional API key management
- —Agent-driven payment and data retrieval in a single HTTP round-trip
Fit
Best for
- —Agents or services that need on-demand invoice data with crypto micropayments
- —Developers experimenting with x402 payment flows on Base
- —Use cases where avoiding API key provisioning is valuable
Not for
- —Production workloads requiring documented request/response schemas
- —Users who need non-crypto (fiat-only) payment options
- —High-volume batch invoice processing where per-call fees add up
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/stripe/invoices/19 \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live (402 challenge captured) and pricing is clear ($0.02 USDC on Base), but there is no documentation, no request/response schema, no examples, and no explanation of what the endpoint actually does beyond its path name. Docs pages are empty. This is effectively a stub listing.
Warnings
- —No OpenAPI spec or request/response schema available
- —All documentation pages (docs, API, pricing, README) render only a wallet-connect prompt with no content
- —The actual behavior and output of /api/v1/stripe/invoices/19 is unknown — the name suggests Stripe invoice data but this is unverified
- —The broader platform lists many endpoints but none have documented schemas
Citations
- —The x402 challenge advertises maxAmountRequired of 20000 base units of USDC on Base network with scheme 'exact'https://lowpaymentfee.com/api/v1/stripe/invoices/19
- —The site lists APIs at $0.02/request with claims of no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 and payTo is 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3https://lowpaymentfee.com/api/v1/stripe/invoices/19