x402basequality 0.30

x402-gated Stripe customer endpoint on Base, paying $0.02 per request in USDC.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com provides premium API access to a Stripe customer resource via the x402 payment protocol. The specific path `/api/v1/stripe/customers/123` suggests it returns or manages Stripe customer data for a given customer ID. Payment is settled on the Base network using USDC (contract 0x8335…2913) with a maximum cost of 20,000 base units, which equals $0.02 per request (USDC uses 6 decimals).

The provider, lowpaymentfee.com, hosts a broader suite of x402-gated APIs spanning data analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance/crypto data feeds, and utility services — all priced uniformly at $0.02 per call. The platform advertises no API keys, no rate limits, and instant access; callers pay per request via the x402 `X-PAYMENT` header on the Base L2 network.

Documentation is extremely sparse. The docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI schema, no request/response examples, and no detailed description of what this particular Stripe customers endpoint returns or accepts as input. The endpoint is confirmed live (returns a proper 402 challenge), but the actual functionality behind the paywall is unclear beyond the name "Premium API Access."

Capabilities

x402-paymentusdc-base-networkstripe-customer-dataper-request-billingno-api-key-required

Use cases

  • Retrieving Stripe customer details without traditional API key management
  • Programmatic access to customer billing data via crypto micropayments
  • Agent-driven workflows that need Stripe customer info with instant, keyless access

Fit

Best for

  • Developers wanting keyless, pay-per-call access to Stripe customer data
  • AI agents that can settle x402 payments on Base in USDC
  • Prototyping integrations where traditional Stripe API key provisioning is undesirable

Not for

  • Production Stripe integrations requiring full CRUD on customer objects (unclear what operations are supported)
  • Users who need detailed documentation or guaranteed SLAs
  • High-volume use cases where $0.02/request adds up vs. direct Stripe API access

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/stripe/customers/123 \
  -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 and returns a valid x402 challenge, but documentation is effectively nonexistent — every doc page shows only 'Connect wallet'. There is no OpenAPI schema, no request/response examples, and no explanation of what the endpoint actually returns. The specific resource path (customers/123) with a hardcoded ID is unusual and raises questions about real utility.

Warnings

  • Documentation pages (docs, API, pricing, README) all render only 'Connect wallet' with no actual content
  • No OpenAPI or schema available — request and response formats are unknown
  • The endpoint path contains a hardcoded customer ID (123), which may be a demo/placeholder rather than a production resource
  • Actual functionality behind the paywall cannot be verified without payment

Citations

Provenance

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

Agent access