x402basequality 0.30

x402-gated Stripe charges 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/charges/75

What it does

This endpoint at lowpaymentfee.com provides "Premium API Access" behind an x402 paywall. 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 utility services — all priced at $0.02 per request and settled in USDC on the Base network.

The specific endpoint `/api/v1/stripe/charges/75` appears to be a Stripe charges proxy or wrapper. The x402 challenge confirms it accepts POST requests, requires payment of up to 20,000 base units of USDC (0x8335…2913 on Base, 6 decimals = $0.02), and settles to address 0x1A2B…85F3. No API keys or rate limits are advertised; access is granted purely via the x402 payment header. The endpoint returns `application/json`.

Documentation is extremely sparse. The landing page lists available endpoints and pricing, but the /docs, /pricing, /api, and /README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI spec, no request/response schema, and no usage examples. The exact functionality behind the "stripe/charges/75" path is unclear — it could be a Stripe charge creation proxy, a charge lookup, or something else entirely. Without documentation or sample payloads, consumers must experiment to determine the input format and response structure.

Capabilities

x402-paymentusdc-basepay-per-requeststripe-chargesjson-apino-api-key

Use cases

  • —Programmatic Stripe charge creation or lookup via a pay-per-call model
  • —Agent-driven payment processing without managing API keys
  • —Integrating Stripe functionality into x402-compatible agent workflows

Fit

Best for

  • —Developers wanting keyless, pay-per-use access to Stripe-related functionality
  • —AI agents that can settle x402 payments in USDC on Base
  • —Prototyping payment flows without Stripe account setup

Not for

  • —Production payment processing requiring well-documented, auditable APIs
  • —Use cases needing detailed request/response schemas and error handling documentation
  • —High-volume Stripe integrations where direct Stripe API access is cheaper and better supported

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/stripe/charges/75 \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <x402-payment-token>" \
  -d '{}'

Endpoint

URLhttps://lowpaymentfee.com/api/v1/stripe/charges/75
Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge with clear pricing ($0.02 USDC on Base). However, there is no OpenAPI spec, no documentation beyond a landing page, no request/response schema, and no examples. The actual functionality of 'stripe/charges/75' is ambiguous. This is effectively a stub listing.

Warnings

  • —No documentation available — /docs, /pricing, /api, and /README all return only a wallet-connect prompt with no content.
  • —No OpenAPI or schema definition; request and response formats are unknown.
  • —The exact purpose of /api/v1/stripe/charges/75 is unclear — 'Premium API Access' is a generic label.
  • —The platform lists many endpoints but none appear to have public documentation describing their behavior.

Citations

Provenance

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

Agent access

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