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 128) 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 specific endpoint probed (/api/v1/stripe/customers/128) costs $0.02 per request (20,000 base units of USDC with 6 decimals). The broader lowpaymentfee.com platform advertises a uniform $0.02/request pricing across a wide catalog of APIs spanning data analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance/crypto market data, and infrastructure utilities. All endpoints are x402-gated — no API keys, no rate limits, and no sign-up required; callers simply attach an X-PAYMENT header with a valid x402 payment proof.
Documentation is extremely sparse. The /docs, /pricing, /api, and /README pages all render only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI spec, no request/response schema documentation, and no example payloads available. The actual behavior of this particular Stripe customers endpoint — what data it returns, what POST body it expects — is unknown from the available material. The endpoint is confirmed live (returns a well-formed 402 challenge).
Capabilities
Use cases
- —Retrieving Stripe customer information via a per-call crypto payment
- —Programmatic access to customer data without traditional API key management
- —Agent-driven workflows that need on-demand Stripe data with instant crypto settlement
Fit
Best for
- —Developers who want keyless, pay-per-use access to Stripe customer data
- —AI agents that can settle x402 payments on Base in USDC
- —Projects needing low-friction API access without subscription commitments
Not for
- —Bulk retrieval of many Stripe customers (no batch endpoint documented)
- —Users who need detailed API documentation or request/response schemas before integrating
- —Anyone without a Base-compatible USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/stripe/customers/128 \
-H "X-PAYMENT: <x402-payment-proof>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but documentation is essentially nonexistent — no OpenAPI spec, no request/response schemas, no examples. The purpose of a 'Stripe customers' endpoint behind a crypto paywall is unclear and potentially concerning from a data-privacy standpoint. Score reflects minimal usable information beyond the 402 challenge itself.
Warnings
- —No API documentation available — /docs, /pricing, /api, and /README all show only 'Connect wallet'
- —No OpenAPI or schema definition; request body and response format are completely unknown
- —Endpoint exposes what appears to be Stripe customer data — unclear data provenance and potential privacy/compliance concerns
- —The specific resource path (/stripe/customers/128) suggests a single hardcoded customer record, which is unusual
Citations
- —Endpoint returns a valid x402 challenge with USDC on Base network at 20,000 base units ($0.02)https://lowpaymentfee.com/api/v1/stripe/customers/128
- —Platform advertises $0.02/request uniform pricing 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/128
- —Documentation pages (/docs, /pricing, /api, /README) render only a 'Connect wallet' prompthttps://lowpaymentfee.com/docs