Stripe customer data endpoint on Base via x402 — pay $0.02 per request in USDC.
What it does
This x402-enabled endpoint at lowpaymentfee.com provides access to a Stripe customer resource (customer ID 186) via a POST request. Payment is settled on the Base network using USDC (contract 0x8335…2913) at a cost of $0.02 per call (20,000 base units with 6 decimals). The endpoint returns application/json and requires no API keys or prior registration — callers simply attach an X-PAYMENT header with a valid x402 payment proof.
The broader lowpaymentfee.com platform advertises a suite of pay-per-call APIs spanning data analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance/crypto market data, and infrastructure utilities, all priced uniformly at $0.02 per request. However, this specific listing is for the Stripe customers endpoint at `/api/v1/stripe/customers/186`, which appears to expose Stripe customer information. No detailed documentation, request/response schemas, or example payloads are available from the crawled pages — the docs, pricing, and API pages all resolve to a minimal "Connect wallet" prompt.
Because the endpoint's actual behavior (what data it returns, what POST body it expects) is undocumented in the crawled material, callers should treat this as an exploratory integration. The x402 challenge is live and well-formed, confirming the endpoint is operational.
Capabilities
Use cases
- —Retrieving Stripe customer details without managing API keys or subscriptions
- —Agent-driven payment workflows that need on-demand Stripe customer data
- —Programmatic access to customer records settled via crypto micropayments
Fit
Best for
- —Developers wanting keyless, pay-per-use access to Stripe customer data
- —AI agents that can settle x402 payments on Base
- —Prototyping integrations where traditional Stripe API key management is undesirable
Not for
- —Production Stripe integrations requiring full CRUD on customer objects (only a single customer ID is exposed)
- —Users who need detailed API documentation or guaranteed SLAs
- —Callers without USDC on Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/stripe/customers/186 \
-H "X-PAYMENT: <x402-payment-proof>" \
-H "Content-Type: application/json"Endpoint
Quality
The x402 challenge is live and well-formed, confirming the endpoint is operational with clear pricing ($0.02 USDC on Base). However, there is no documentation for request/response schemas, no example payloads, and the docs pages are empty. The endpoint's purpose (Stripe customer data for a single hardcoded ID) is narrow and unexplained.
Warnings
- —No request or response schema documented — callers must discover the expected POST body experimentally.
- —Endpoint targets a single Stripe customer ID (186); unclear if this is a demo or production resource.
- —All documentation pages (docs, pricing, API, README) returned only a 'Connect wallet' prompt with no useful content.
- —The nature of the data returned (potentially PII from Stripe) is undocumented — exercise caution regarding data sensitivity.
Citations
- —The x402 challenge returns maxAmountRequired of 20000 in USDC (6 decimals) on Base, equaling $0.02 per request.https://lowpaymentfee.com/api/v1/stripe/customers/186
- —The platform advertises uniform $0.02/request pricing with no API keys, no rate limits, and instant access on Base network.https://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base.https://lowpaymentfee.com/api/v1/stripe/customers/186