x402-gated premium API access on Base, paid per-call in USDC.
What it does
This endpoint at lowpaymentfee.com provides "Premium API Access" behind an x402 paywall. It is one of many endpoints offered by the lowpaymentfee.com platform, which hosts a variety of API categories including Data & Analytics, AI & Machine Learning, Finance & Web3, and Infrastructure utilities. All endpoints on the platform follow the same pay-per-request model with no API keys, no rate limits, and instant access.
The specific endpoint `/api/v1/stripe/charges/121` accepts POST requests and is gated by an x402 challenge on the Base network. Payment is in USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) at a maximum cost of $0.02 per request (20,000 base units with 6 decimals). The payment is settled on-chain to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a timeout of 300 seconds.
However, the exact functionality behind this particular endpoint path (`/stripe/charges/121`) is unclear. The name "Premium API Access" and the path referencing "stripe/charges" do not match any of the documented API categories on the landing page. Documentation pages (/docs, /api, /pricing, /README) all returned only a "Connect wallet" prompt with no substantive content. Without further documentation or example responses, the actual data or service returned by this endpoint cannot be confirmed.
Capabilities
Use cases
- —Programmatic access to a premium API endpoint with per-call USDC micropayments
- —Agent-driven workflows that need keyless, pay-as-you-go API access on Base
- —Testing x402 payment flows against a live endpoint
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents that can settle USDC payments on Base L2
- —Use cases requiring no-signup, no-API-key access
Not for
- —Users who need clear documentation of what the endpoint returns before paying
- —High-volume use cases where per-call crypto settlement overhead matters
- —Anyone without a Base-compatible USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/stripe/charges/121 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but the actual functionality behind this specific path is undocumented. All documentation pages return only 'Connect wallet' with no content. No request/response schema, no examples, and the endpoint name ('Premium API Access' at /stripe/charges/121) is generic and unexplained.
Warnings
- —The exact functionality of /api/v1/stripe/charges/121 is unknown — the path suggests Stripe charge processing but no documentation confirms this.
- —All documentation pages (/docs, /api, /pricing, /README) returned only 'Connect wallet' with no substantive content.
- —No request body schema or response schema is documented; callers cannot know what to send or what to expect back.
- —This endpoint path does not appear in the landing page's listed APIs, raising questions about whether it is a standard offering.
Citations
- —The endpoint returns a 402 x402 challenge with USDC on Base network at maxAmountRequired 20000https://lowpaymentfee.com/api/v1/stripe/charges/121
- —Platform advertises $0.02/request pricing with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/stripe/charges/121
- —Documentation pages return only 'Connect wallet' with no substantive contenthttps://lowpaymentfee.com/docs