x402-gated Stripe customer data endpoint on Base, paid per-request in USDC.
What it does
This endpoint at lowpaymentfee.com provides access to a specific Stripe customer resource (customer ID 176) behind an x402 paywall. The endpoint accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x8335…2913) via the x402 "exact" scheme. The maximum amount required per call is 20,000 base units of USDC, which equals $0.02 USD (USDC uses 6 decimals).
The broader lowpaymentfee.com platform advertises a variety of API categories including Data & Analytics, AI & Machine Learning, Finance & Web3, and Infrastructure utilities — all priced at $0.02 per request with no API keys, no rate limits, and instant access. However, this specific listing is for the Stripe customers endpoint only. The crawled documentation pages (docs, pricing, README) returned minimal content (just a "Connect wallet" prompt), so detailed request/response schemas and field-level documentation are unavailable.
Because the endpoint path references Stripe customers, it likely returns customer metadata (e.g., name, email, subscription status) for the given customer ID. Without an OpenAPI spec or example responses, the exact output fields remain unknown. The x402 challenge was successfully captured (HTTP 402 with valid accepts array), confirming the endpoint is live and properly configured.
Capabilities
Use cases
- —Retrieving Stripe customer metadata without managing API keys or subscriptions
- —Agent-driven lookups of customer billing information via micropayment
- —Programmatic access to customer records with per-call USDC payment
Fit
Best for
- —AI agents needing on-demand Stripe customer data without credential management
- —Developers who want pay-per-use access to customer records
- —Web3-native applications settling API costs in USDC on Base
Not for
- —Bulk customer data exports requiring thousands of calls (cost adds up at $0.02 each)
- —Users who need detailed API documentation or guaranteed SLAs
- —Applications requiring non-crypto payment methods
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/stripe/customers/176 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The x402 challenge is live and well-formed, confirming the endpoint exists and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI spec, no request/response schema, and all documentation pages returned only a 'Connect wallet' stub. The purpose of the endpoint (Stripe customer data) is inferred solely from the URL path.
Warnings
- —No OpenAPI or request/response schema available — exact input parameters and output fields are unknown.
- —Documentation pages (/docs, /pricing, /README) returned no meaningful content.
- —The endpoint references a hardcoded Stripe customer ID (176); unclear if other IDs are accessible or what data is returned.
- —The platform advertises many API categories but crawled content is extremely thin — actual functionality behind each endpoint is unverified.
Citations
- —The x402 challenge returns maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/stripe/customers/176
- —The platform advertises $0.02 per request with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/stripe/customers/176