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/172` suggests a Stripe-related charges endpoint, though the crawled documentation does not describe this particular route in detail. The x402 challenge confirms the endpoint is live, accepting POST requests, and requires a maximum payment of 20,000 base units of USDC (0.02 USD) per call.
The broader lowpaymentfee.com platform advertises a suite of APIs spanning data & analytics (metrics, reports, data export, insights), AI & machine learning (sentiment analysis, text summarization, classification, embeddings), finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints are uniformly priced at $0.02 per request with no API keys, no rate limits, and no minimum commitments. Payments settle on the Base network using USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913).
Documentation is extremely sparse — the /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI spec, no request/response schema documentation, and no example payloads available. The specific behavior of the `/api/v1/stripe/charges/172` route (what it returns, what input it expects) is unknown from the available material.
Capabilities
Use cases
- —Programmatic access to a premium API resource without traditional API key management
- —Agent-driven workflows that need to pay per-call in USDC on Base
- —Integrating x402-compatible payment flows into automated pipelines
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents that can settle USDC payments on Base L2
- —Use cases requiring keyless, pay-as-you-go API access
Not for
- —Users who need detailed API documentation or OpenAPI specs before integrating
- —Production workloads requiring guaranteed SLAs or support
- —Users without a Base-compatible USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/stripe/charges/172 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is confirmed live via a valid x402 402 challenge, and pricing is clear ($0.02 USDC per call). However, there is no OpenAPI spec, no request/response schema, no documentation beyond a wallet-connect prompt, and the specific purpose of this particular route (/api/v1/stripe/charges/172) is undocumented. This is effectively a stub listing.
Warnings
- —No OpenAPI or schema documentation available for this endpoint
- —The /docs, /pricing, /api, and /README pages all render only 'Connect wallet' with no usable content
- —The specific behavior and expected input/output of /api/v1/stripe/charges/172 is unknown
- —The route path references 'stripe/charges' which may imply Stripe integration, but no details are provided
Citations
- —The endpoint returns a 402 x402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/stripe/charges/172
- —All endpoints are priced at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/stripe/charges/172
- —Documentation pages (/docs, /api, /pricing, /README) render only a 'Connect wallet' prompthttps://lowpaymentfee.com/docs