x402-gated Stripe customer endpoint on Base, paying per-call in USDC.
What it does
This endpoint at lowpaymentfee.com exposes a specific Stripe customer resource (`/api/v1/stripe/customers/86`) behind an x402 paywall. It accepts POST requests and charges up to $0.02 per call in USDC on the Base network. Payment is handled via the x402 protocol's "exact" scheme — callers attach an X-PAYMENT header with a signed payment to the specified wallet address, and the endpoint returns an `application/json` response.
The broader lowpaymentfee.com platform advertises a suite of pay-per-request APIs spanning data analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance/crypto market data, and infrastructure utilities — all priced at $0.02 per request with no API keys, no rate limits, and no commitments. However, the specific endpoint listed here (`/stripe/customers/86`) is not prominently documented on the site's landing page, and its exact functionality is unclear. It likely proxies or wraps a Stripe customer record, but no request/response schema documentation was found.
The x402 challenge is live and well-formed, confirming the endpoint is operational. The payment asset is USDC (contract `0x8335...2913` on Base), with a max amount of 20,000 base units ($0.02 given 6 decimals). Documentation beyond the landing page is extremely thin — the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no additional content.
Capabilities
Use cases
- —Retrieving or interacting with a Stripe customer record via a crypto-paywall
- —Programmatic access to Stripe data without traditional API key management
- —Agent-driven payment flows where per-call USDC settlement is preferred
Fit
Best for
- —Developers wanting keyless, pay-per-call access to Stripe customer data
- —AI agents that can settle x402 payments in USDC on Base
- —Prototyping crypto-gated API access patterns
Not for
- —Production Stripe integrations requiring full CRUD on customer objects
- —Users who need detailed API documentation or guaranteed SLAs
- —Non-crypto workflows that cannot produce x402 payment headers
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/stripe/customers/86 \
-H "X-PAYMENT: <signed-x402-payment-header>" \
-H "Content-Type: application/json"Endpoint
Quality
The x402 challenge is live and well-formed, confirming the endpoint works. However, there is no request/response schema, no documentation beyond a wallet-connect prompt, and the specific endpoint (/stripe/customers/86) is not listed among the site's advertised APIs. The purpose and behavior of this endpoint must be inferred.
Warnings
- —No request or response schema documentation available
- —The specific endpoint /api/v1/stripe/customers/86 is not listed on the provider's landing page among advertised APIs
- —All documentation pages (docs, API, pricing, README) render only 'Connect wallet' with no content
- —Unclear what data this endpoint returns or what POST body it expects
- —The endpoint path suggests it wraps a specific Stripe customer record — potential PII/data sensitivity concerns
Citations
- —The x402 challenge returns maxAmountRequired of 20000 base units in USDC on Base (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913), equaling $0.02https://lowpaymentfee.com/api/v1/stripe/customers/86
- —The site advertises $0.02/request pricing with no API keys, no rate limits, and instant access on the Base networkhttps://lowpaymentfee.com
- —Documentation pages render only a 'Connect wallet' prompt with no additional contenthttps://lowpaymentfee.com/docs