x402-gated Stripe invoice endpoint on Base, pay-per-call with USDC.
What it does
This endpoint at lowpaymentfee.com provides "Premium API Access" behind an x402 payment challenge. The specific resource path (`/api/v1/stripe/invoices/191`) suggests it returns or processes a Stripe invoice identified by ID 191. Payment is settled on the Base network using USDC (contract 0x8335…2913) with a maximum cost of $0.02 per request (20,000 base units at 6 decimals). The endpoint accepts HTTP POST requests and returns application/json.
The broader lowpaymentfee.com platform advertises a suite of pay-per-request APIs spanning data analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance/crypto data feeds, and infrastructure utilities — all priced at $0.02 per call with no API keys, no rate limits, and no commitments. However, this specific listing is for the Stripe invoices endpoint, and no documentation was found describing its request body schema, expected parameters, or response format. The docs, pricing, API, and README pages all returned only a "Connect wallet" prompt with no substantive content.
Because there is no OpenAPI spec, no request/response examples, and no documentation beyond the x402 challenge itself, the actual functionality of this endpoint remains unclear. It may retrieve invoice details, create invoices, or perform some other Stripe-related operation, but this cannot be confirmed from available materials.
Capabilities
Use cases
- —Retrieving or processing Stripe invoice data via a crypto-gated endpoint
- —Programmatic invoice access without traditional API keys
- —Agent-driven invoice workflows settled with USDC on Base
Fit
Best for
- —Developers wanting keyless, pay-per-call access to Stripe invoice data
- —AI agents that can settle x402 challenges on Base with USDC
- —Users who prefer crypto micropayments over subscription billing
Not for
- —Anyone needing documented request/response schemas before integration
- —High-volume invoice processing where $0.02/call adds up significantly
- —Users without USDC on the Base network
Quick start
# 1. Send a POST to the endpoint — you'll get a 402 with payment details
curl -X POST https://lowpaymentfee.com/api/v1/stripe/invoices/191
# 2. Parse the 402 JSON challenge, sign an x402 payment for 20000 base-unit USDC on Base
# 3. Resend the POST with the X-PAYMENT header containing the signed payment proofEndpoint
Quality
The x402 challenge is live and parseable, confirming the endpoint exists and its pricing. However, there is zero documentation on request parameters, response schema, or actual functionality. The docs/pricing/API pages are empty stubs. This is effectively a stub listing.
Warnings
- —No OpenAPI spec or request/response schema available
- —All documentation pages (docs, pricing, API, README) return only a 'Connect wallet' prompt with no content
- —The actual behavior of /api/v1/stripe/invoices/191 is unknown — no examples or descriptions beyond the generic 'Premium API Access' label
- —The endpoint path suggests Stripe invoice access but this is unconfirmed
Citations
- —The endpoint returns a 402 challenge with x402Version 1, accepting USDC on Base with maxAmountRequired of 20000 base unitshttps://lowpaymentfee.com/api/v1/stripe/invoices/191
- —The platform advertises all APIs at $0.02/request with no API keys, no rate limits, and instant access on the Base networkhttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/stripe/invoices/191