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

What it does

This endpoint at lowpaymentfee.com provides "Premium API Access" behind an x402 paywall. The specific path `/api/v1/stripe/charges/180` appears to be part of a broader platform offering numerous pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all priced at $0.02 per request settled in USDC on the Base network.

The x402 challenge confirms the endpoint is live and accepts POST requests. Payment is made via the x402 "exact" scheme to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` using USDC (contract `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`) on Base. The `maxAmountRequired` is 20000 base units, which at 6 decimals equals $0.02. The endpoint returns `application/json`.

However, the specific functionality of the `/api/v1/stripe/charges/180` path is unclear. The name suggests it may relate to Stripe charge operations (possibly creating or retrieving a charge of a specific amount), but no documentation, request schema, or response schema is available beyond the x402 challenge metadata. The broader site lists many API categories but the crawled docs, pricing, and API pages all rendered only a "Connect wallet" prompt with no additional content. Without input/output schemas or usage examples, the actual behavior of this endpoint remains opaque.

Capabilities

x402-paymentusdc-settlementbase-networkpay-per-requestjson-responsestripe-charges

Use cases

  • Programmatically creating or querying Stripe charges via a pay-per-call model
  • Integrating payment processing into agent workflows without API key management
  • Testing x402 payment flows on the Base network

Fit

Best for

  • Developers experimenting with x402 payment protocols
  • Agents needing stateless pay-per-call access without subscriptions
  • Low-volume or sporadic API usage where $0.02/request is cost-effective

Not for

  • High-volume payment processing where per-call fees add up quickly
  • Use cases requiring detailed API documentation and guaranteed SLAs
  • Production systems needing well-documented input/output contracts

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02 USDC on Base), but there is no documentation, no input/output schema, and no explanation of what the endpoint actually does. The docs, pricing, and API pages all render only a wallet-connect prompt. The specific purpose of '/api/v1/stripe/charges/180' is ambiguous.

Warnings

  • No input or output schema available — the actual request format and response structure are unknown
  • Documentation pages (docs, pricing, API, README) all render only 'Connect wallet' with no useful content
  • The specific functionality of /api/v1/stripe/charges/180 is unclear — 'Stripe charges' could mean many things
  • No examples or error documentation available

Citations

Provenance

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

Agent access