x402basequality 0.30

x402-gated Stripe invoice endpoint on Base, paying per-call in 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/134`) behind an x402 paywall. The provider operates a broader platform offering dozens of pay-per-call APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services — all settled on the Base network using USDC via the x402 protocol.

The specific endpoint listed here is labeled "Premium API Access" and costs up to $0.02 per request (maxAmountRequired of 20,000 base units of USDC with 6 decimals). It accepts HTTP POST requests and returns `application/json`. Payment is made to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` on Base, using the USDC contract at `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`. The x402 challenge specifies a 300-second payment timeout.

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 spec, no request/response schema documentation, and no explanation of what data the Stripe invoice endpoint actually returns. The provider's landing page confirms the $0.02/request pricing model and advertises no API keys, no rate limits, and instant access, but gives no detail about the specific invoice endpoint's behavior or required POST body.

Capabilities

x402-paymentusdc-settlementbase-networkstripe-invoice-accesspay-per-callno-api-key

Use cases

  • Retrieving Stripe invoice data via a per-call USDC micropayment
  • Programmatic access to invoice #134 without traditional API key management
  • Agent-driven financial data retrieval settled on Base L2

Fit

Best for

  • Developers who want keyless, pay-per-call access to Stripe invoice data
  • AI agents that can settle x402 payments in USDC on Base
  • Users who prefer crypto micropayments over subscription billing

Not for

  • Anyone needing detailed API documentation or request/response schemas before integrating
  • Bulk invoice retrieval across many invoice IDs (this endpoint targets a single invoice)
  • Users without USDC on Base network

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/stripe/invoices/134 \
  -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 (402 challenge captured) and pricing is clear ($0.02/request in USDC on Base). However, there is no documentation, no OpenAPI spec, no request body schema, no response schema, and no explanation of what the endpoint actually returns. The docs/pricing/API pages are all empty wallet-connect stubs. This is effectively a stub listing.

Warnings

  • No documentation available — docs, API, pricing, and README pages all show only 'Connect wallet' with no content.
  • No request body schema or response schema provided; it is unclear what POST body is expected or what data is returned.
  • This endpoint targets a single hardcoded invoice ID (134); unclear if this is a demo or production resource.
  • No OpenAPI or ai-plugin manifest found.

Citations

Provenance

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

Agent access

x402-gated Stripe invoice endpoint on Base, paying per-call in USDC. — Clawmart · Clawmart