x402-gated Stripe customer endpoint on Base, paying $0.02 per request in USDC.
What it does
This endpoint at lowpaymentfee.com exposes a specific Stripe customer resource (`/api/v1/stripe/customers/15`) behind an x402 paywall. It is part of a broader platform that offers dozens of pay-per-call APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services — all priced at $0.02 per request, settled in USDC on the Base network.
The x402 challenge confirms the endpoint is live and accepts POST requests. Payment is made via the x402 "exact" scheme to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3`, with a max amount of 20,000 base units of USDC (0x8335…2913 on Base, 6 decimals), which equals $0.02. The response MIME type is `application/json`. No API keys or rate limits are advertised; access is gated purely by the per-request micropayment.
Documentation on the site is extremely thin — the docs, pricing, API, and README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI schema, no request/response examples, and no description of what the `/api/v1/stripe/customers/15` endpoint actually returns or what input it expects. The endpoint path suggests it retrieves or manipulates a Stripe customer record (ID 15), but the exact functionality is unverified. The platform lists many other endpoints (analytics, AI, finance, utilities) at the same price point, but none have documented schemas either.
Capabilities
Use cases
- —Retrieving or interacting with a Stripe customer record via a crypto-micropayment gate
- —Demonstrating x402 payment protocol integration for per-call billing
- —Accessing pay-per-use API infrastructure without traditional API key management
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents that need keyless, pay-per-call API access on Base
- —Projects requiring Stripe customer data access via crypto micropayments
Not for
- —Production use requiring documented request/response schemas
- —High-volume Stripe integrations where direct Stripe API access is cheaper and better documented
- —Users without USDC on Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/stripe/customers/15 \
-H "X-PAYMENT: <x402_payment_token>" \
-H "Content-Type: application/json"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 schema, no request/response examples, and the purpose of this specific Stripe customer endpoint is unclear. Docs pages render only 'Connect wallet' with no content.
Warnings
- —No OpenAPI schema or request/response documentation available
- —All documentation pages (docs, pricing, API, README) render only a 'Connect wallet' prompt with no useful content
- —The specific functionality of /api/v1/stripe/customers/15 is undocumented — it is unclear what data it returns or what POST body it expects
- —The endpoint references a hardcoded Stripe customer ID (15), which may be a demo or placeholder
Citations
- —Endpoint returns 402 with x402 challenge, maxAmountRequired 20000 in USDC on Basehttps://lowpaymentfee.com/api/v1/stripe/customers/15
- —Platform advertises $0.02 per request, no API keys, no rate limits, Base networkhttps://lowpaymentfee.com
- —Docs, pricing, API, and README pages render only 'Connect wallet'https://lowpaymentfee.com/docs