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 130) 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 suite of APIs spanning data analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance/crypto data feeds, and infrastructure utilities — all priced at $0.02 per request with no API keys, no rate limits, and no commitments. However, this specific endpoint (/api/v1/stripe/customers/130) is not listed among the publicly advertised APIs on the homepage. Its purpose appears to be retrieving or interacting with a particular Stripe customer record, though no documentation or schema details are available beyond the x402 challenge.
The endpoint is live and returns a valid x402 challenge (HTTP 402) with version 1 of the protocol. No OpenAPI spec, detailed docs, or example responses were found during crawling — the docs, pricing, and API pages all render only a "Connect wallet" prompt with no additional content.
Capabilities
Use cases
- —Retrieving Stripe customer information via a pay-per-call model without API key management
- —Programmatic access to customer billing data settled in USDC on Base
- —Agent-driven workflows that need Stripe customer details with crypto-native payment
Fit
Best for
- —Developers who want keyless, pay-per-request access to Stripe customer data
- —AI agents that can settle x402 payments in USDC on Base
- —Prototyping integrations where traditional Stripe API key provisioning is undesirable
Not for
- —Bulk retrieval of many Stripe customers (each call costs $0.02 and targets a single customer ID)
- —Users who need comprehensive Stripe API coverage (only one customer resource is exposed here)
- —Anyone without a Base-compatible USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/stripe/customers/130 \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but there is no OpenAPI spec, no documentation, no example request/response schemas, and the specific endpoint (/stripe/customers/130) is not listed among the site's advertised APIs. The docs and other pages render only a wallet-connect prompt with no useful content.
Warnings
- —No documentation or OpenAPI schema available — all doc pages render only 'Connect wallet'
- —This specific endpoint (/api/v1/stripe/customers/130) is not listed among the site's publicly advertised APIs
- —The endpoint targets a hardcoded customer ID (130); unclear if other customer IDs are accessible via different paths
- —No example request or response body is available; actual returned data structure is unknown
- —Potential sensitivity: endpoint may expose Stripe customer PII — verify compliance requirements before use
Citations
- —The x402 challenge requires a maximum of 20,000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/stripe/customers/130
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/stripe/customers/130
- —The site advertises $0.02 per request with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —Docs, pricing, API, and README pages render only a 'Connect wallet' prompthttps://lowpaymentfee.com/docs