x402-gated Stripe customer endpoint on Base, pay-per-call with USDC.
What it does
This endpoint at lowpaymentfee.com exposes a Stripe customer resource (`/api/v1/stripe/customers/56`) behind an x402 paywall. It accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (contract `0x8335…2913`) with an exact-scheme challenge. The maximum amount required per call is 20,000 base units of USDC, which equals $0.02 (USDC uses 6 decimals).
The broader lowpaymentfee.com platform advertises a wide catalog of pay-per-request APIs spanning data analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance/crypto market data, and utility services—all priced at $0.02 per request with no API keys, no rate limits, and no commitments. However, this specific listing is for the Stripe customers endpoint, whose exact functionality is not documented beyond the title "Premium API Access." No OpenAPI schema, request/response examples, or detailed documentation were found in the crawl; the docs, API, pricing, and README pages all rendered only a wallet-connect prompt with no substantive content.
Because the endpoint is live (returning a valid 402 challenge) but lacks any documentation about what the Stripe customer resource actually returns or what POST body it expects, agents should treat this as a minimally documented endpoint. The price is clear and low ($0.02/call), and the x402 wire protocol is standard, but the absence of input/output schemas means callers will need to experiment or obtain documentation out-of-band.
Capabilities
Use cases
- —Retrieving Stripe customer information via a pay-per-call model without needing API keys
- —Programmatic access to Stripe customer records settled with USDC on Base
- —Agent-driven workflows that need on-demand Stripe customer data with crypto micropayments
Fit
Best for
- —Developers who want keyless, pay-per-use access to Stripe customer data
- —AI agents with USDC on Base that need to fetch payment platform records
- —Prototyping integrations where traditional Stripe API key management is undesirable
Not for
- —Production systems requiring well-documented request/response schemas
- —Use cases needing bulk or batch Stripe data retrieval at scale
- —Users without USDC on the Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/stripe/customers/56
# Returns 402 with x402 challenge; attach X-PAYMENT header with valid USDC payment on Base to access.Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge, confirming it is operational. However, there is no documentation, no OpenAPI schema, no request/response examples, and no explanation of what the Stripe customer endpoint actually does or accepts. The crawled pages beyond the homepage were empty wallet-connect stubs. This is effectively a stub listing.
Warnings
- —No documentation found — docs, API, pricing, and README pages all render only a wallet-connect prompt with no content.
- —No input or output schema available; callers cannot know what POST body to send or what response to expect.
- —The specific purpose of '/api/v1/stripe/customers/56' (a hardcoded customer ID) is unclear — it may be a demo or placeholder.
- —The endpoint path references a specific Stripe customer ID (56), which may not generalize to other customer IDs.
Citations
- —The endpoint returns a 402 challenge with x402Version 1, exact scheme, on Base network, requiring up to 20000 base units of USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913).https://lowpaymentfee.com/api/v1/stripe/customers/56
- —The platform advertises $0.02/request pricing with no API keys, no rate limits, and instant access on the Base network.https://lowpaymentfee.com
- —The platform lists APIs across data/analytics, AI/ML, finance/Web3, and infrastructure categories.https://lowpaymentfee.com