x402basequality 0.30

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

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com provides access to a specific Stripe customer resource (customer ID 175) via the x402 payment protocol. It is part of a broader platform that offers dozens of pay-per-request API endpoints spanning data analytics, AI/ML inference, finance, crypto, and utility services — all gated behind x402 micropayments settled in USDC on the Base network.

The specific endpoint `/api/v1/stripe/customers/175` is listed as "Premium API Access" and costs up to 20,000 base units of USDC (i.e., $0.02 USD, since USDC uses 6 decimals). Payment is made via the x402 exact scheme: callers attach an `X-PAYMENT` header with a signed payment to the designated wallet address. No API keys, rate limits, or upfront commitments are required — each request is individually paid for at the time of the call.

The platform's landing page advertises a uniform $0.02/request pricing model across all endpoints. Documentation, however, is extremely thin — the /docs, /pricing, /api, and /README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI spec, no request/response schema documentation, and no examples of what the Stripe customer endpoint actually returns. The endpoint is confirmed live (returns a proper 402 challenge), but the lack of documentation makes it difficult to know what data is served or what POST body (if any) is expected.

Capabilities

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

Use cases

  • Retrieving Stripe customer information for customer ID 175 via a single paid request
  • Integrating x402-gated data access into agent workflows without API key management
  • Programmatic access to payment-provider customer records settled on-chain

Fit

Best for

  • Agents or services that need on-demand Stripe customer data without subscription overhead
  • Developers experimenting with x402 micropayment-gated APIs
  • Workflows requiring keyless, per-call API access on Base

Not for

  • Bulk retrieval of many Stripe customers (single-resource endpoint, $0.02 each)
  • Users who need detailed API documentation or response schemas before integrating
  • Anyone needing non-USDC or non-Base-network payment options

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is confirmed live with a valid x402 402 challenge, but there is zero documentation on request format, expected POST body, or response schema. The /docs, /pricing, and /README pages are empty beyond a wallet-connect prompt. No OpenAPI spec exists. The purpose of the endpoint (Stripe customer data) is only inferred from the URL path and title.

Warnings

  • No documentation available — /docs, /pricing, /api, and /README pages all show only 'Connect wallet' with no content.
  • No OpenAPI or schema definition for request or response payloads.
  • The specific data returned by this Stripe customer endpoint is unknown; 'Premium API Access' is a generic label.
  • It is unclear whether a POST body is required or what fields it should contain.
  • The endpoint serves a single customer ID (175); unclear if other customer IDs are available or if this is a demo.

Citations

Provenance

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

Agent access