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 32). It is part of a broader platform offering dozens of pay-per-call API endpoints spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all gated behind x402 payment challenges settled in USDC on the Base network.

The specific endpoint `/api/v1/stripe/customers/32` is listed under "Premium API Access" and accepts POST requests. The x402 challenge advertises a maximum cost of 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 per request (USDC uses 6 decimals). Payment is made via the x402 "exact" scheme to the specified payTo address, with a 300-second timeout. No API keys or rate limits are advertised; access is purely payment-gated.

Documentation on the site is extremely thin — the docs, API, pricing, 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 endpoint actually returns. The endpoint's purpose (retrieving or managing a Stripe customer record) can only be inferred from the URL path. The platform's landing page confirms uniform $0.02/request pricing across all endpoints and settlement on the Base network.

Capabilities

x402-payment-gatedusdc-base-settlementstripe-customer-apipay-per-requestno-api-key-required

Use cases

  • Retrieving Stripe customer data without traditional API key authentication
  • Programmatic access to customer records via crypto-native micropayments
  • Agent-driven workflows that need on-demand Stripe customer information

Fit

Best for

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

Not for

  • Production Stripe integrations requiring full CRUD on customer objects (unclear what operations are supported)
  • Users needing detailed API documentation or response schema guarantees
  • 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/32 \
  -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 documentation, no OpenAPI spec, no request/response examples, and the actual functionality of this specific Stripe customer endpoint is entirely unclear. Docs pages render only 'Connect wallet' with no content.

Warnings

  • No API documentation available — docs, API, pricing, and README pages all show only 'Connect wallet'
  • No OpenAPI or JSON schema describing request parameters or response format
  • The purpose of accessing '/api/v1/stripe/customers/32' (a hardcoded customer ID) is unclear — it may be a demo or placeholder
  • No information on what data is returned or what POST body is expected

Citations

Provenance

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

Agent access