x402-gated Stripe customer data endpoint on Base, paid per-call in USDC.
What it does
This endpoint at lowpaymentfee.com provides access to a specific Stripe customer resource (customer ID 115) behind an x402 paywall. It is part of a broader platform that offers dozens of pay-per-request API endpoints spanning data analytics, AI/ML inference, finance, crypto, and utility services — all settled on the Base network using USDC.
The specific endpoint `/api/v1/stripe/customers/115` is labeled "Premium API Access" and accepts HTTP POST requests. Payment is handled via the x402 protocol: callers receive a 402 challenge specifying the USDC asset on Base (contract 0x8335…2913), with a maximum amount of 20,000 base units. Since USDC uses 6 decimals, this translates to $0.02 per request, consistent with the platform's advertised flat pricing of $0.02/request across all endpoints. The payTo address is 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 and the timeout is 300 seconds.
The platform advertises no API keys, no rate limits, and instant access. However, documentation is extremely sparse — the /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no request/response examples, and no description of what data this particular endpoint actually returns. The endpoint path suggests it retrieves or interacts with a Stripe customer record, but the exact input parameters and response format are unknown.
Capabilities
Use cases
- —Retrieving Stripe customer information via a pay-per-request model without API key management
- —Programmatic access to customer billing data settled in USDC on Base
- —Agent-driven workflows that need on-demand Stripe customer lookups with crypto payment
Fit
Best for
- —Developers who want keyless, pay-per-call access to Stripe customer data
- —AI agents that can settle x402 payments in USDC on Base
- —Users who prefer crypto micropayments over traditional subscription billing
Not for
- —Anyone needing detailed API documentation or response schema before integrating
- —High-volume use cases where $0.02/request adds up significantly compared to direct Stripe API access
- —Users without USDC on the Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/stripe/customers/115 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge with clear pricing, but there is no documentation, no OpenAPI schema, no request/response examples, and no explanation of what the endpoint actually returns. The purpose (Stripe customer data?) is inferred solely from the URL path. Docs pages are empty stubs.
Warnings
- —No API documentation available — /docs, /api, /pricing, and /README pages all show only 'Connect wallet' with no content
- —No OpenAPI or input/output schema provided; request parameters and response format are completely unknown
- —The endpoint path suggests access to a specific Stripe customer record (ID 115), but there is no confirmation of what data is returned
- —The broader platform lists many endpoint categories (AI, analytics, finance, etc.) but none have documented schemas
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units in USDC on Basehttps://lowpaymentfee.com/api/v1/stripe/customers/115
- —Platform advertises $0.02/request flat pricing with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/stripe/customers/115
- —Documentation pages (/docs, /api, /pricing, /README) render only a 'Connect wallet' prompthttps://lowpaymentfee.com/docs