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 34) via a POST request. It is part of a broader platform that offers dozens of pay-per-call API endpoints spanning data analytics, AI/ML inference, finance/Web3 data, and utility services — all gated behind x402 payment challenges on the Base network using USDC.

The specific endpoint `/api/v1/stripe/customers/34` is labeled "Premium API Access" and costs $0.02 per request (20,000 base units of USDC with 6 decimals = $0.02). Payment is settled on-chain on Base to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` using USDC (`0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`). The x402 challenge specifies a 300-second timeout and uses the "exact" payment scheme.

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 description of what data this endpoint actually returns. The platform advertises no API keys, no rate limits, and instant access, but the actual functionality behind this particular Stripe customer endpoint is unclear from available materials.

Capabilities

x402-paymentusdc-settlementbase-networkpay-per-requeststripe-customer-datapost-method

Use cases

  • Retrieving Stripe customer data for customer ID 34 via a paid API call
  • Demonstrating x402 payment protocol integration with USDC on Base
  • Agent-driven programmatic access to gated API resources without API keys

Fit

Best for

  • Developers experimenting with x402 payment protocol
  • Agents needing keyless, pay-per-call API access on Base
  • Projects requiring on-chain payment-gated API endpoints

Not for

  • Production Stripe integrations requiring full customer CRUD operations
  • Users who need detailed API documentation or OpenAPI specs before integrating
  • High-volume use cases where per-request crypto payments add friction

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/stripe/customers/34 \
  -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, confirming it is operational. However, documentation is essentially nonexistent — all doc pages show only 'Connect wallet'. There is no OpenAPI schema, no request/response examples, and the actual purpose of a 'Stripe customers/34' endpoint is unexplained. Pricing is clear ($0.02/request) but functionality is opaque.

Warnings

  • No API documentation available — all doc pages render only 'Connect wallet'
  • No OpenAPI or output schema describing what this endpoint returns
  • The endpoint targets a hardcoded Stripe customer ID (34); unclear if this is a demo or production resource
  • No request body schema documented; unknown what POST payload is expected
  • No response examples available anywhere in crawled content

Citations

Provenance

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

Agent access

x402-gated Stripe customer endpoint on Base, pay $0.02 per request in USDC. — Clawmart · Clawmart