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 180) behind an x402 paywall. It accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x8335…2913) via the x402 "exact" scheme.

The endpoint charges a maximum of 20,000 base units of USDC per request. Since USDC uses 6 decimals, this equals $0.02 per call — consistent with the provider's site-wide flat pricing of $0.02/request. The provider advertises no API keys, no rate limits, and instant access; the only gate is the x402 payment header.

The broader lowpaymentfee.com platform lists many additional endpoints across data/analytics, AI/ML, finance/Web3, and infrastructure categories, all at the same $0.02/request price point. However, this specific listing covers only the `/api/v1/stripe/customers/180` resource. Documentation on the site is extremely thin — the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI spec, no request/response schema documentation, and no explanation of what data the Stripe customer endpoint actually returns.

Capabilities

x402-paymentusdc-settlementbase-networkstripe-customer-datajson-responseper-call-pricing

Use cases

  • Retrieving Stripe customer information via a pay-per-call model without API key management
  • Agent-driven workflows that need on-demand access to Stripe customer records
  • Programmatic access to customer data settled in USDC on Base L2

Fit

Best for

  • Developers who want keyless, pay-per-request access to Stripe customer data
  • AI agents with USDC wallets on Base that need to fetch customer records
  • Prototyping integrations where traditional Stripe API key provisioning is impractical

Not for

  • Bulk retrieval of many Stripe customers (each call costs $0.02 and only targets a single customer ID)
  • Users who need detailed API documentation or response schema guarantees before integrating
  • Anyone without a Base-compatible USDC wallet

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/stripe/customers/180 \
  -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), but there is virtually no documentation: no OpenAPI spec, no request/response schema, no explanation of what data is returned. The docs pages are empty beyond a wallet-connect prompt. The endpoint path suggests Stripe customer data but this is unverified. Pricing is clear at $0.02/call.

Warnings

  • No API documentation available — docs, API, pricing, and README pages all show only 'Connect wallet' with no content.
  • No request or response schema is documented; callers cannot know what fields to send or expect back.
  • The endpoint targets a hardcoded customer ID (180); it is unclear whether this is a demo or production resource.
  • The nature of the returned Stripe customer data is completely undocumented.

Citations

Provenance

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

Agent access