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
Endpoint
https://lowpaymentfee.com/api/v1/stripe/customers/33

What it does

This endpoint at lowpaymentfee.com provides x402-protocol access to a Stripe customer resource (customer ID 33) via a POST request. Payment is settled on the Base network using USDC (contract 0x8335…2913) with an exact-scheme challenge. The max amount required is 20,000 base units, which at 6 decimals equals $0.02 per call.

The broader lowpaymentfee.com platform advertises a suite of pay-per-request APIs spanning data & analytics (metrics, reports, data export, insights), AI & machine learning (sentiment analysis, text summarization, classification, embeddings), finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints are listed at $0.02 per request with no API keys, no rate limits, and no minimum commitments.

The specific endpoint probed (/api/v1/stripe/customers/33) is labeled "Premium API Access" and returns a valid x402 challenge (HTTP 402). However, documentation is extremely sparse — 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 examples of what this Stripe customer endpoint actually returns. The purpose of exposing a Stripe customer record behind a paywall is unclear and should be verified before use.

Capabilities

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

Use cases

  • —Retrieving Stripe customer data for customer ID 33 via a single paid POST request
  • —Demonstrating x402 payment protocol integration with USDC on Base
  • —Agent-driven access to paywalled API resources without API key management

Fit

Best for

  • —Developers experimenting with x402 payment protocol
  • —Agents needing keyless, pay-per-request API access on Base
  • —Testing USDC micropayment flows

Not for

  • —Production Stripe integrations requiring authenticated access to your own customer data
  • —Use cases needing detailed API documentation or guaranteed SLAs
  • —Bulk data retrieval where per-request pricing is cost-prohibitive

Quick start

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

Endpoint

URLhttps://lowpaymentfee.com/api/v1/stripe/customers/33
Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 402 challenge, but documentation is essentially nonexistent — all doc pages show only 'Connect wallet'. There is no OpenAPI spec, no request/response schema, and no explanation of what the Stripe customer endpoint actually returns. The purpose of the specific resource is unclear.

Warnings

  • —No API documentation available — /docs, /api, /pricing, and /README all render only a wallet-connect prompt
  • —No OpenAPI or schema definition found for any endpoint
  • —The purpose of exposing a Stripe customer record (customer 33) behind a paywall is unclear and potentially sensitive
  • —No response schema or example responses available to verify what data is returned
  • —The platform lists many endpoints on its homepage but none have documented schemas

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/ghe9JX
x402-gated Stripe customer endpoint on Base, pay $0.02 per request in USDC. — Clawmart · Clawmart