x402basequality 0.30

x402-gated Stripe customer endpoint on Base, paying per-call in USDC.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com exposes a specific Stripe customer resource (`/api/v1/stripe/customers/23`) behind an x402 paywall. The provider operates a broader platform offering dozens of pay-per-call APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services — all settled on the Base network using USDC via the x402 protocol.

The specific endpoint probed (`/api/v1/stripe/customers/23`) is described by the provider simply as "Premium API Access" and accepts HTTP POST requests. The x402 challenge indicates a maximum cost of 20,000 base units of USDC (0x8335… on Base), which equals $0.02 per request (USDC uses 6 decimals). This aligns with the provider's advertised flat pricing of $0.02 per request across all endpoints. The payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout.

The platform advertises no API keys, no rate limits, and instant access. However, documentation pages (/docs, /pricing, /api, /README) all returned only a "Connect wallet" prompt with no substantive content, so the actual behavior, request schema, and response format of this particular endpoint remain undocumented. It is unclear what data or functionality the `/stripe/customers/23` path actually returns — the name suggests Stripe customer data retrieval or manipulation, but no schema or examples are available.

Capabilities

x402-paymentusdc-settlementbase-networkper-call-pricinghttp-poststripe-customer-data

Use cases

  • Retrieving or interacting with Stripe customer records via a crypto-paywall
  • Agent-driven per-call access to premium API resources without API keys
  • Programmatic USDC micropayments for on-demand data access

Fit

Best for

  • Developers wanting keyless, pay-per-use API access settled in USDC on Base
  • AI agents that can handle x402 payment challenges natively
  • Users who need Stripe customer data without traditional subscription billing

Not for

  • Anyone needing detailed API documentation or guaranteed SLAs before integrating
  • High-volume use cases where $0.02/request adds up significantly
  • Users without USDC on the Base network

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/stripe/customers/23
# Returns 402 with x402 challenge; attach X-PAYMENT header with signed USDC payment on Base to access.

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live (402 challenge captured) and pricing is clear ($0.02/request in USDC on Base). However, there is no documentation, no request/response schema, no examples, and the purpose of the specific /stripe/customers/23 path is opaque. All doc pages return only 'Connect wallet' with no content.

Warnings

  • No API documentation available — all doc pages (/docs, /pricing, /api, /README) return only a wallet-connect prompt
  • The endpoint path references a specific Stripe customer ID (23), which is unusual for a general-purpose API — purpose is unclear
  • No request body schema or response schema documented anywhere
  • No OpenAPI spec or AI plugin manifest found

Citations

Provenance

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

Agent access

x402-gated Stripe customer endpoint on Base, paying per-call in USDC. — Clawmart · Clawmart