x402-gated Stripe customer endpoint on Base, pay $0.02 per request in USDC.
What it does
This endpoint at lowpaymentfee.com provides x402-protocol access to a Stripe customer resource (customer ID 89). It is part of a broader platform offering dozens of pay-per-call API endpoints across data analytics, AI/ML inference, finance/Web3, and infrastructure utilities — all gated via the x402 payment protocol on the Base network.
The specific endpoint `/api/v1/stripe/customers/89` is labeled "Premium API Access" and accepts POST requests. Payment is settled in USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Base, with a maximum amount required of 20,000 base units — which at 6 decimals equals $0.02 per request. The platform advertises uniform $0.02/request pricing across all its endpoints, with no API keys, no rate limits, and no minimum commitments.
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 examples of what the endpoint actually returns. The endpoint's purpose — retrieving or interacting with a Stripe customer record — can only be inferred from the URL path. Without documentation, it is unclear what request body is expected or what response payload is returned.
Capabilities
Use cases
- —Retrieving Stripe customer data via a pay-per-call model without API key management
- —Programmatic access to customer billing information settled in USDC on Base
- —Agent-driven workflows that need on-demand Stripe customer lookups with crypto payment
Fit
Best for
- —Developers wanting keyless, pay-per-use access to Stripe customer data
- —AI agents that can settle x402 payments in USDC on Base
- —Projects needing low-friction API access without subscription commitments
Not for
- —Production systems requiring documented request/response schemas and SLAs
- —Users who need bulk Stripe customer queries at scale (no documented rate limits but no guarantees either)
- —Anyone without a Base-compatible USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/stripe/customers/89 \
-H "X-PAYMENT: <x402-payment-header>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live (returns a valid x402 402 challenge) and pricing is clear ($0.02 USDC on Base). However, there is no documentation, no OpenAPI spec, no request/response examples, and the purpose of this specific endpoint (Stripe customer 89) is opaque. The docs pages are all blank wallet-connect prompts.
Warnings
- —No documentation available — /docs, /api, /pricing, and /README all show only 'Connect wallet' with no content
- —No OpenAPI or schema definition; request body and response format are completely unknown
- —The endpoint references a specific Stripe customer ID (89) — unclear if this is a demo, a shared resource, or a real customer record
- —Purpose and functionality of this specific endpoint can only be guessed from the URL path
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units in USDC on Basehttps://lowpaymentfee.com/api/v1/stripe/customers/89
- —Platform advertises $0.02/request pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/stripe/customers/89
- —Documentation pages (/docs, /api, /pricing, /README) render only a 'Connect wallet' prompthttps://lowpaymentfee.com/docs