x402basequality 0.35

x402-gated Stripe invoice endpoint on Base, pay-per-call with USDC.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com exposes a specific Stripe invoice resource (`/api/v1/stripe/invoices/153`) behind an x402 paywall. It is part of a broader platform that offers dozens of pay-per-request APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services — all settled on the Base network using USDC.

The x402 challenge confirms the endpoint is live and accepts POST requests. The price for this particular resource is 20,000 base units of USDC (asset `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913` on Base), which equals $0.02 USD (USDC uses 6 decimals). Payment is made via the x402 "exact" scheme to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3`, with a maximum timeout of 300 seconds.

The platform advertises a uniform $0.02 per request across all endpoints, with no API keys, no rate limits, and instant access. However, documentation pages (docs, pricing, README) all returned only a "Connect wallet" prompt with no substantive content, so the actual request/response schema for this Stripe invoices endpoint is unknown. It is unclear what data this endpoint returns — it could be invoice details, invoice creation, or some other Stripe-related operation. Without documentation or example payloads, agents must discover the behavior empirically.

Capabilities

x402-paymentusdc-settlementbase-networkstripe-invoicepay-per-requestno-api-key

Use cases

  • Retrieving or creating Stripe invoice data via a single paid API call
  • Programmatic access to invoice information without traditional API key management
  • Agent-driven financial workflows that need invoice data on demand

Fit

Best for

  • Agents needing Stripe invoice access without managing API keys
  • Developers experimenting with x402 payment-gated APIs
  • Micropayment-based access to financial data

Not for

  • Production Stripe integrations requiring full Stripe API coverage and documentation
  • Use cases needing detailed request/response schemas before integration
  • High-volume invoice processing where $0.02 per call adds up significantly

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.35/ 1.00

The x402 challenge is live and pricing is clear ($0.02 USDC on Base), but there is no documentation, no request/response schema, and no examples. The docs, pricing, and README pages all returned only 'Connect wallet' with no content. The purpose of this specific Stripe invoices endpoint is ambiguous.

Warnings

  • No documentation available — all doc pages return only 'Connect wallet' with no content
  • Request and response schemas are completely unknown for this endpoint
  • The purpose of '/api/v1/stripe/invoices/153' is unclear — it references a specific invoice ID which may be a demo or placeholder
  • No OpenAPI spec, no ai-plugin manifest, no agents.txt detected

Citations

Provenance

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

Agent access