x402basequality 0.35

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 x402-protocol access to a Stripe customer resource at `/api/v1/stripe/customers/5`. It is part of a broader platform offering dozens of pay-per-call API endpoints spanning data analytics, AI/ML inference, finance, crypto, and utility services — all gated behind x402 payment challenges settled in USDC on the Base network.

The specific endpoint probed (`/api/v1/stripe/customers/5`) returned a live 402 challenge requesting up to 20,000 base units of USDC (0x8335…2913 on Base, 6 decimals), which equals $0.02 per request. Payment is made via the x402 "exact" scheme to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3, with a 300-second timeout. The endpoint accepts POST requests and returns `application/json`.

The platform advertises a uniform $0.02/request pricing across all its endpoints, with no API keys, no rate limits, and no minimum commitments. However, documentation beyond the landing page is essentially empty (all doc/pricing/API pages only show a "Connect wallet" prompt), so the actual response schema and behavior of this particular Stripe customers endpoint are unknown. It is unclear what data this endpoint returns or what input it expects beyond a POST body.

Capabilities

x402-paymentusdc-settlementbase-networkstripe-customer-datapay-per-requestno-api-keyjson-response

Use cases

  • Retrieving Stripe customer data via a crypto-settled pay-per-call model
  • Agent-driven access to premium API resources without traditional API key management
  • Programmatic access to financial/customer data with USDC micropayments on Base

Fit

Best for

  • Developers or agents who want keyless, pay-per-use API access settled in USDC
  • Use cases requiring on-chain payment proof for API calls
  • Scenarios where avoiding subscription commitments is preferred

Not for

  • Users needing detailed API documentation or response schema guarantees before integrating
  • High-volume use cases where per-request pricing at $0.02 may be costly compared to bulk plans
  • Anyone without a Base-compatible USDC wallet

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.35/ 1.00

The endpoint is live and returns a valid x402 challenge with clear pricing, but there is no documentation, no input/output schema, and no examples. All doc pages render only a wallet-connect prompt. The purpose and response format of this specific Stripe customers endpoint are entirely opaque.

Warnings

  • No documentation available — all doc/pricing/API pages show only 'Connect wallet' with no content.
  • No input or output schema provided for this endpoint; request body format is unknown.
  • The endpoint path references a specific Stripe customer ID (5), but it is unclear whether this is a real resource or a demo placeholder.
  • The broader platform lists many endpoint categories but none have documented schemas or example responses.

Citations

Provenance

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

Agent access