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/179`) behind an x402 paywall. When called without payment, it returns a 402 challenge requesting USDC on the Base network. The endpoint accepts POST requests and returns JSON.
The parent site lowpaymentfee.com advertises a broad catalog of pay-per-call APIs spanning data analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance/crypto market data, and utility services (geocoding, validation, conversion). All listed endpoints are priced at $0.02 per request with no API keys, no rate limits, and no commitments required. However, the specific endpoint being listed here (`/api/v1/stripe/invoices/179`) is not among the publicly advertised catalog entries and its x402 challenge shows a maxAmountRequired of 20,000 base units of USDC (6 decimals), which equals $0.02 — consistent with the site's uniform pricing.
Documentation is extremely sparse. The docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no request/response examples, and no description of what data this particular invoice endpoint returns. The endpoint is live and responding with a valid x402 challenge, but the actual functionality behind the paywall is unclear.
Capabilities
Use cases
- —Retrieving Stripe invoice data (invoice #179) via a micropayment-gated call
- —Programmatic access to invoice details without traditional API key authentication
- —Agent-driven payment and data retrieval in a single HTTP round-trip
Fit
Best for
- —Agents or scripts that need to fetch specific Stripe invoice data and can pay per-call in USDC
- —Developers exploring x402 payment protocol integrations
- —Use cases where keyless, pay-as-you-go API access is preferred
Not for
- —Bulk invoice retrieval or batch processing (single-resource endpoint)
- —Users who need detailed documentation or guaranteed SLAs before integrating
- —Anyone without a Base-network USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/stripe/invoices/179 \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but there is zero documentation on what the endpoint actually returns. No OpenAPI spec, no request/response examples, and the docs pages are empty. The specific resource path (/stripe/invoices/179) is not listed in the site's public catalog, making its purpose unclear.
Warnings
- —No documentation available — docs, API, pricing, and README pages all show only 'Connect wallet' with no content.
- —This specific endpoint (/api/v1/stripe/invoices/179) is not listed in the site's public API catalog; its purpose and response format are unknown.
- —No OpenAPI schema or example responses are provided anywhere.
- —The endpoint appears to serve a single fixed resource (invoice 179) rather than a parameterized API.
Citations
- —The site advertises all endpoints at $0.02 per request with no API keys, no rate limits, and instant access on Base network.https://lowpaymentfee.com
- —The x402 challenge shows maxAmountRequired of 20000 base units of USDC (asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Base network.https://lowpaymentfee.com/api/v1/stripe/invoices/179
- —The site lists API categories including Data & Analytics, AI & Machine Learning, Finance & Web3, and Infrastructure.https://lowpaymentfee.com
- —Docs, API, pricing, and README pages render only a 'Connect wallet' prompt with no substantive content.https://lowpaymentfee.com/docs