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 on the Base network. The specific endpoint path `/api/v1/stripe/charges/115` suggests a Stripe-related charges resource, though the crawled documentation does not describe this particular route in detail. The provider's landing page advertises a broad suite of APIs spanning data & analytics, AI/ML (sentiment analysis, summarization, classification, embeddings), finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation) — all at a flat $0.02 per request.
The x402 challenge for this specific endpoint advertises a maximum cost of 20,000 base units of USDC (0x8335… on Base), which equals $0.02 given USDC's 6 decimals. Payment is made via the x402 "exact" scheme to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout. No API keys or rate limits are required — callers simply attach the X-PAYMENT header with a valid x402 payment proof.
Documentation beyond the landing page is extremely thin: the /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI spec, no request/response schema documentation, and no examples for this or any other endpoint. The actual behavior and response format of `/api/v1/stripe/charges/115` is unknown from the available material.
Capabilities
Use cases
- —Making per-call paid API requests without API key management
- —Programmatic access to a Stripe charges resource via crypto micropayment
- —Agent-driven workflows that need keyless, pay-as-you-go endpoint access
Fit
Best for
- —Developers wanting zero-signup API access paid in USDC on Base
- —AI agents that can attach x402 payment headers autonomously
- —Prototyping integrations without committing to subscription plans
Not for
- —Users who need 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-network USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/stripe/charges/115 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-proof>"Endpoint
Quality
The endpoint is live (402 challenge captured) and pricing is clear ($0.02 USDC on Base), but there is no documentation, no OpenAPI spec, no request/response schema, and no examples. The purpose of this specific route (/api/v1/stripe/charges/115) is unclear. Docs pages return only 'Connect wallet' with no content.
Warnings
- —No OpenAPI spec or schema documentation available for this endpoint
- —All documentation pages (/docs, /api, /pricing, /README) render only 'Connect wallet' with no useful content
- —The specific purpose and expected input/output of /api/v1/stripe/charges/115 is undocumented
- —The endpoint path references 'stripe/charges' but payment is via x402/USDC — the relationship to Stripe is unclear
Citations
- —The x402 challenge advertises maxAmountRequired of 20000 base units of USDC on Base with a 300-second timeouthttps://lowpaymentfee.com/api/v1/stripe/charges/115
- —The provider advertises $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —The provider lists APIs across data & analytics, AI/ML, finance & Web3, and infrastructure categorieshttps://lowpaymentfee.com
- —Documentation pages /docs, /api, /pricing, /README all show only 'Connect wallet'https://lowpaymentfee.com/docs