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. It is part of a broader platform offering dozens of pay-per-call APIs spanning data & analytics, AI/ML inference, finance & Web3 data, and infrastructure utilities — all priced at $0.02 per request settled in USDC on the Base network.
The specific endpoint `/api/v1/stripe/charges/153` sits under the Stripe charges path, suggesting it returns or processes information related to a Stripe charge object (charge ID 153). However, no detailed documentation, request schema, or response schema is available — the docs, API, pricing, and README pages all resolve to a minimal "Connect wallet" prompt with no further content. The x402 challenge confirms the endpoint is live: it returns a 402 with an `exact` payment scheme requiring up to 20,000 base units of USDC (0x8335… on Base), which equals $0.02 given USDC's 6 decimals.
The platform advertises no API keys, no rate limits, and instant access. Payment is made via the x402 protocol's X-PAYMENT header. The payTo address is `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3`. Because the endpoint path references Stripe charges, it likely wraps or proxies Stripe payment data, but the exact request/response format is undocumented.
Capabilities
Use cases
- —Retrieving Stripe charge details via a pay-per-call model without API key management
- —Agents autonomously purchasing payment/charge data on-chain
- —Integrating Stripe charge information into Web3 workflows
Fit
Best for
- —Developers wanting keyless, pay-per-use access to Stripe charge data
- —AI agents that can settle x402 payments in USDC on Base
- —Prototyping integrations where traditional Stripe API key provisioning is undesirable
Not for
- —Production Stripe integrations where you already have direct Stripe API access
- —Use cases requiring detailed documentation or guaranteed SLAs
- —High-volume batch processing where per-request pricing adds up
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/stripe/charges/153 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is confirmed live via a valid 402 challenge with clear pricing ($0.02 USDC on Base). However, there is no documentation, no request/response schema, no examples, and the docs pages are empty stubs. The purpose of this specific charges/153 path is unclear.
Warnings
- —No request or response schema available — the exact payload format is unknown.
- —Documentation pages (/docs, /api, /pricing, /README) all render only a 'Connect wallet' prompt with no useful content.
- —The endpoint path '/api/v1/stripe/charges/153' references a hardcoded charge ID (153); it is unclear whether this is a generic endpoint or specific to one charge.
- —The platform lists many API categories (AI, analytics, finance, etc.) but none have visible documentation — treat all claims with caution.
Citations
- —The endpoint returns HTTP 402 with x402 version 1 challenge requiring up to 20,000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/stripe/charges/153
- —Platform advertises $0.02 per request, no API keys, no rate limits, instant access, Base networkhttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/stripe/charges/153