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 x402-protocol access to a Stripe customer resource (customer ID 79). It is part of a broader platform offering pay-per-call APIs across data analytics, AI/ML inference, finance, and utility categories — all priced at $0.02 per request, settled in USDC on the Base network. No API keys, rate limits, or upfront commitments are required; callers simply attach an x402 payment header to each request.

The specific endpoint `/api/v1/stripe/customers/79` is labeled "Premium API Access" in the x402 challenge. The challenge advertises a maxAmountRequired of 20,000 base units of USDC (0x8335… on Base), which equals $0.02 given USDC's 6 decimals. The payment scheme is "exact" with a 300-second timeout window. The endpoint accepts POST requests and returns application/json.

Documentation on the platform is extremely thin — the /docs, /pricing, /api, and /README pages all render only a wallet-connect prompt with no substantive content. There is no OpenAPI spec, no request/response schema, and no explanation of what data this particular Stripe customer endpoint returns or what input it expects. The landing page confirms the platform's general pricing model and lists many other endpoints, but provides no details about the Stripe-specific resource. Prospective callers should be aware that the actual behavior and response format of this endpoint are undocumented.

Capabilities

x402-paymentusdc-settlementbase-networkstripe-customer-datapay-per-requestno-api-key

Use cases

  • Retrieving Stripe customer data via a single paid API call without needing a Stripe account
  • Agent-driven workflows that need to fetch customer payment info on demand
  • Demonstrating x402 protocol payment flows with a live endpoint

Fit

Best for

  • Developers experimenting with x402 payment protocol
  • Agents that need one-off Stripe customer lookups without managing API keys
  • Low-volume, pay-as-you-go access to payment platform data

Not for

  • Production Stripe integrations (use Stripe's own API for full access and reliability)
  • High-volume batch processing where per-request fees add up
  • Use cases requiring documented request/response schemas

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live (returns a valid x402 402 challenge) and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI spec, no request/response schema, no documentation beyond a landing page listing, and no examples. The purpose of a 'Stripe customers/79' resource behind x402 is unclear and undocumented.

Warnings

  • No documentation available — /docs, /pricing, /api, and /README pages all render only a wallet-connect prompt with no content.
  • No OpenAPI or request/response schema provided; callers cannot know what to send or what to expect back.
  • The purpose and data returned by /api/v1/stripe/customers/79 is unexplained — it may expose third-party Stripe customer data, raising potential privacy concerns.
  • The endpoint path references a hardcoded customer ID (79), which is unusual for a general-purpose API.

Citations

Provenance

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

Agent access

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