x402basequality 0.30

x402-gated Stripe customer endpoint on Base, pay $0.02 per request in USDC.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com provides premium API access to a Stripe customers resource via the x402 payment protocol. The specific route `/api/v1/stripe/customers/3` appears to be one of many pay-per-call endpoints offered by the provider, which spans categories including data analytics, AI/ML inference, finance, and infrastructure utilities. All endpoints on the platform are priced at $0.02 per request, settled in USDC on the Base network.

The x402 challenge confirms the endpoint is live and accepts POST requests. Payment is made via the "exact" scheme to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` using USDC (contract `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`) on Base. The max amount required is 20,000 base units, which equals $0.02 (USDC uses 6 decimals). The timeout is 300 seconds. No API keys or rate limits are advertised — access is purely payment-gated.

Documentation is extremely sparse. The docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no additional content. There is no OpenAPI spec, no request/response schema documentation, and no explanation of what the Stripe customers endpoint actually returns or what parameters it accepts. The endpoint's purpose — whether it proxies Stripe customer data, creates customers, or performs some other operation — cannot be determined from available material.

Capabilities

x402-paymentusdc-settlementbase-networkstripe-customerspay-per-requestno-api-keypost-method

Use cases

  • Accessing Stripe customer data without managing API keys
  • Programmatic pay-per-call access to a Stripe customers resource
  • Agent-driven payment-gated API consumption on Base

Fit

Best for

  • Developers wanting keyless, pay-per-use API access
  • AI agents that can settle x402 payments in USDC on Base
  • Quick prototyping without subscription commitments

Not for

  • Production use requiring documented request/response schemas
  • High-volume use cases where per-request pricing adds up
  • Users needing detailed Stripe API documentation or support

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/stripe/customers/3 \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <x402-payment-token>"

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge with clear pricing. However, there is no documentation, no OpenAPI spec, no request/response schema, and no explanation of what the Stripe customers endpoint actually does. The docs pages are empty beyond a wallet-connect prompt. This is effectively a stub listing.

Warnings

  • No documentation available — docs, API, pricing, and README pages all show only 'Connect wallet'
  • No OpenAPI or schema describing request parameters or response format
  • Purpose of the /api/v1/stripe/customers/3 endpoint is unclear — it may proxy Stripe data but this is unverified
  • No examples of successful responses available

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-19 09:51:25Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-25

Agent access