x402-gated Stripe charges endpoint on Base, paying $0.02 per request in USDC.
What it does
This endpoint at lowpaymentfee.com provides "Premium API Access" behind an x402 payment wall. The specific resource `/api/v1/stripe/charges/123` accepts POST requests and requires a per-call USDC payment on the Base network. The x402 challenge advertises a maxAmountRequired of 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimals. Payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout.
The provider's landing page lists a broad catalog of API categories — data & analytics, AI & machine learning, finance & Web3, and infrastructure utilities — all priced at $0.02 per request with no API keys, no rate limits, and instant access. However, the specific endpoint being listed here (`/api/v1/stripe/charges/123`) appears to be a Stripe charges resource, which doesn't clearly map to any of the documented categories. No OpenAPI schema, request/response examples, or detailed documentation were found; the docs, pricing, and API pages all returned only a "Connect wallet" prompt with no substantive content.
Because the endpoint path references "stripe/charges/123" — suggesting it may proxy or wrap a Stripe charge lookup or creation — its exact functionality is unclear from available materials. The x402 challenge confirms the endpoint is live and accepting payment-gated POST requests, but what it returns after payment is not documented.
Capabilities
Use cases
- —Programmatic access to a Stripe charges resource via x402 micropayment
- —Agent-driven payment flows where no API key registration is needed
- —Exploring x402 protocol integration with USDC on Base
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents that need keyless, pay-per-call API access on Base
- —Use cases requiring low-friction micropayment-gated endpoints
Not for
- —Users needing well-documented API contracts with clear request/response schemas
- —Production workloads requiring guaranteed SLAs or detailed error handling documentation
- —Anyone looking for free or subscription-based API access
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/stripe/charges/123 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-header>" \
-d '{}'Example
Request
{
"url": "https://lowpaymentfee.com/api/v1/stripe/charges/123",
"body": {},
"method": "POST",
"headers": {
"X-PAYMENT": "<x402-payment-header>",
"Content-Type": "application/json"
}
}Endpoint
Quality
The x402 challenge is live and confirms pricing and payment details, but there is no OpenAPI schema, no request/response documentation, and no examples. The endpoint path (stripe/charges/123) is ambiguous and undocumented. Docs pages returned only wallet-connect prompts with no content.
Warnings
- —No OpenAPI or schema documentation available for this endpoint
- —Docs, pricing, and API pages all render only a 'Connect wallet' prompt with no substantive content
- —The endpoint path '/api/v1/stripe/charges/123' references a specific charge ID — unclear if this is a demo, a proxy, or a real Stripe resource
- —Exact request body format and response structure are unknown
Citations
- —x402 challenge returns maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/stripe/charges/123
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/stripe/charges/123
- —All listed APIs priced at $0.02 per request with no API keys, no rate limits, instant accesshttps://lowpaymentfee.com
- —Payment timeout is 300 seconds, payTo address is 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3https://lowpaymentfee.com/api/v1/stripe/charges/123