x402-gated premium API access on Base, paid per-call in USDC at $0.02/request.
What it does
This endpoint at lowpaymentfee.com provides "Premium API Access" behind an x402 paywall, settling payments in USDC on the Base network. The specific resource path `/api/v1/stripe/charges/129` suggests a Stripe-related charges endpoint, though the crawled documentation does not describe this particular route in detail. The broader lowpaymentfee.com platform advertises a wide catalog of pay-per-call APIs spanning data analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance/Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation).
The x402 challenge confirms the endpoint is live and accepts POST requests. It requires an exact-scheme payment of up to 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 per request (USDC uses 6 decimals). The platform emphasizes simplicity: no API keys, no rate limits, no minimum commitments — just attach an X-PAYMENT header with a valid x402 payment proof. The payTo address is 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout.
Documentation beyond the landing page is extremely thin — the /docs, /api, /pricing, and /README pages all returned only a "Connect wallet" prompt with no substantive content. There is no OpenAPI spec, no request/response schema, and no description of what this specific charges/129 endpoint returns. The endpoint's purpose must be inferred from its URL path and the generic "Premium API Access" label.
Capabilities
Use cases
- —Programmatic access to Stripe charge data behind a crypto paywall
- —Agent-driven per-call API consumption without traditional API key management
- —Demonstrating x402 payment flows for USDC on Base
Fit
Best for
- —Developers experimenting with x402 payment protocol integrations
- —AI agents that need keyless, pay-per-call API access
- —Users who prefer crypto micropayments over subscription billing
Not for
- —Users needing detailed API documentation or OpenAPI specs before integrating
- —High-volume use cases where per-call pricing at $0.02 adds up significantly
- —Anyone without a Base-compatible USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/stripe/charges/129 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-proof>"Endpoint
Quality
The x402 challenge is live and pricing is clear ($0.02/request in USDC on Base), but there is no OpenAPI spec, no request/response schema, and no documentation for this specific endpoint. The docs, pricing, and README pages are all empty beyond a wallet-connect prompt. The actual functionality of /api/v1/stripe/charges/129 is unknown.
Warnings
- —No OpenAPI spec or request/response schema available
- —Documentation pages (/docs, /pricing, /README) contain no substantive content
- —The specific purpose and response format of /api/v1/stripe/charges/129 is undocumented
- —Cannot verify what data or service this endpoint actually provides
Citations
- —The endpoint returns a 402 x402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/stripe/charges/129
- —Platform advertises $0.02/request pricing with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/stripe/charges/129