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 at `/api/v1/stripe/customers/98`. 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/98`) 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 wallet `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3`, with a 300-second timeout. The endpoint accepts POST requests and returns `application/json`.

The platform advertises a uniform $0.02/request pricing model across all its endpoints, with no API keys, no rate limits, and no minimum commitments. Documentation pages (`/docs`, `/pricing`, `/api`, `/README`) all returned only a "Connect wallet" prompt with no substantive content, so the actual request/response schemas for this Stripe customer endpoint are unknown. It is unclear what data this endpoint returns or what POST body it expects — the name "Premium API Access" and the path suggest it may proxy or wrap Stripe customer data, but this is not confirmed by any documentation.

Capabilities

x402-paymentusdc-basepay-per-callstripe-customer-datajson-response

Use cases

  • Retrieving Stripe customer information via a crypto-gated pay-per-call interface
  • Agent-driven access to financial or customer data without API key provisioning
  • Programmatic micropayment-based API consumption on Base L2

Fit

Best for

  • Agents or services that need keyless, pay-per-call access to Stripe customer data
  • Developers experimenting with x402 protocol integrations
  • Scenarios requiring no-commitment, no-rate-limit API access

Not for

  • Production use cases requiring well-documented request/response schemas
  • High-volume Stripe integrations where direct Stripe API access is cheaper and better documented
  • Users who need non-crypto payment options

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/stripe/customers/98 \
  -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, but there is zero documentation on request/response schemas, no OpenAPI spec, and all doc pages are empty stubs. The purpose of this specific Stripe customer endpoint is unclear, making it effectively a stub listing.

Warnings

  • No documentation available — all doc pages (/docs, /pricing, /api, /README) return only a wallet-connect prompt with no content.
  • Request body schema and response schema are completely unknown for this endpoint.
  • The endpoint path references a specific Stripe customer ID (98), which may indicate a demo or placeholder resource rather than a general-purpose API.
  • The relationship between this endpoint and actual Stripe data is unverified.

Citations

Provenance

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

Agent access