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 170) behind an x402 paywall. The provider operates a broad platform offering dozens of pay-per-call API endpoints across categories like data analytics, AI/ML inference, finance, and infrastructure utilities — all settled on the Base network using USDC.
The specific endpoint `/api/v1/stripe/customers/170` is listed as "Premium API Access" and accepts 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 provider's advertised flat pricing of $0.02/request across all endpoints. No API keys are required; access is granted upon valid x402 payment. The provider advertises no rate limits and instant access.
Documentation is extremely sparse — the /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI schema, no request/response examples, and no explanation of what data the endpoint actually returns for a Stripe customer resource. The endpoint's purpose (retrieving Stripe customer details, performing an action on a customer record, etc.) is not documented anywhere in the crawled material.
Capabilities
Use cases
- —Retrieving Stripe customer information via a crypto-paid API call
- —Programmatic access to payment platform customer records without traditional API keys
- —Agent-driven workflows that need Stripe data and can settle in USDC on Base
Fit
Best for
- —Developers who want keyless, pay-per-call access to Stripe customer data
- —AI agents with x402-compatible wallets on Base
- —Projects needing low-friction API access without subscription commitments
Not for
- —Users who need detailed API documentation or response schemas before integrating
- —Bulk retrieval of many Stripe customers (no batch endpoint documented)
- —Anyone without a Base-network USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/stripe/customers/170 \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge with clear pricing ($0.02 USDC on Base). However, documentation is essentially nonexistent — no OpenAPI spec, no request/response schemas, no explanation of what the endpoint returns. The purpose of exposing a single Stripe customer record (ID 170) is unclear and undocumented.
Warnings
- —No documentation available — /docs, /api, /pricing, and /README pages all show only 'Connect wallet' with no content.
- —No OpenAPI or output schema provided; response format is completely unknown.
- —The endpoint targets a specific customer ID (170); it is unclear whether this is a demo resource or production data.
- —No request body schema documented; callers cannot know what parameters to send.
- —The nature of 'Premium API Access' for a Stripe customer record is unexplained — potential data privacy concerns.
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units in USDC on Base network.https://lowpaymentfee.com/api/v1/stripe/customers/170
- —The provider advertises $0.02/request flat pricing with no API keys, no rate limits, and instant access.https://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913.https://lowpaymentfee.com/api/v1/stripe/customers/170
- —Documentation pages (/docs, /api, /pricing, /README) render only a 'Connect wallet' prompt.https://lowpaymentfee.com/docs