x402-gated Stripe charges endpoint on Base, pay $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 route `/api/v1/stripe/charges/200` appears to be part of a broader platform offering dozens of pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3 data, and utility services — all priced at $0.02 per request.
The endpoint accepts POST requests and is gated by an x402 challenge on the Base network. Payment is made in USDC (contract 0x8335…2913) to address 0x1A2B…85F3, with a maximum amount of 20,000 base units (i.e., $0.02 given USDC's 6 decimals). The challenge specifies a 300-second timeout and returns application/json responses. No API keys or rate limits are advertised; access is purely payment-gated.
Documentation is extremely sparse — 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 explanation of what the `/stripe/charges/200` endpoint actually returns or what input it expects. The endpoint name suggests it may proxy or wrap Stripe charge creation, but this is speculative. The platform's landing page lists many API categories but provides no detail on any individual endpoint's behavior or schema.
Capabilities
Use cases
- —Programmatic Stripe charge creation or retrieval behind a crypto paywall
- —Agent-initiated payment operations without API key management
- —Pay-per-use access to financial infrastructure endpoints
Fit
Best for
- —Developers wanting keyless, pay-per-call API access on Base
- —AI agents that can settle x402 USDC payments autonomously
- —Prototyping payment flows without Stripe account setup
Not for
- —Production Stripe integrations requiring full Stripe API feature coverage
- —Users who need detailed API documentation before integrating
- —High-volume use cases where per-request pricing is inefficient
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/stripe/charges/200 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge with clear pricing ($0.02 USDC on Base). However, there is no OpenAPI spec, no request/response schema, no documentation beyond a wallet-connect prompt, and no explanation of what the endpoint actually does. The listing is effectively a stub.
Warnings
- —No API documentation available — /docs, /api, /pricing, /README all show only 'Connect wallet'
- —No OpenAPI or schema definition; request body format and response structure are unknown
- —Endpoint purpose is unclear — 'stripe/charges/200' could mean charge creation, retrieval, or something else entirely
- —No agents.txt or robots.txt present
Citations
- —The endpoint returns a 402 x402 challenge with maxAmountRequired of 20000 USDC base units on Base networkhttps://lowpaymentfee.com/api/v1/stripe/charges/200
- —All listed APIs are priced at $0.02 per request 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/200