x402basequality 0.30

x402-gated Stripe invoice endpoint on Base, paying $0.02 in USDC per request.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com provides access to a Stripe invoice resource (invoice ID 162) behind an x402 paywall. The provider operates a broader platform offering pay-per-request APIs across data analytics, AI/ML inference, finance/Web3, and infrastructure utilities — all priced at $0.02 per call and settled in USDC on the Base network.

The specific endpoint `/api/v1/stripe/invoices/162` is labeled "Premium API Access" in the x402 challenge. It accepts POST requests and returns `application/json`. Payment is made via the x402 exact scheme: the caller includes an X-PAYMENT header containing a signed USDC transfer of up to 20,000 base units (i.e., $0.02, since USDC uses 6 decimals) to the provider's address on Base. No API keys or rate limits are advertised; access is purely payment-gated.

Documentation is extremely sparse — the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI spec, no request/response schema beyond the x402 challenge's outputSchema stub, and no description of what the invoice endpoint actually returns. The endpoint is confirmed live (402 challenge captured), but the lack of documentation makes it difficult to know what data or functionality is delivered after payment.

Capabilities

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

Use cases

  • Retrieving Stripe invoice data (invoice 162) via a single paid API call
  • Demonstrating x402 payment-gated API access on Base
  • Integrating pay-per-request invoice lookups into agent workflows

Fit

Best for

  • Developers experimenting with x402 payment protocols
  • Agents that need on-demand invoice data without API key management
  • Users who prefer per-call USDC micropayments over subscriptions

Not for

  • Users who need detailed API documentation or response schemas before integrating
  • Bulk invoice retrieval across many invoice IDs (only invoice 162 is exposed at this path)
  • Non-crypto users who cannot settle payments in USDC on Base

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/stripe/invoices/162 \
  -H "X-PAYMENT: <signed-x402-payment-header>" \
  -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 with clear pricing ($0.02 USDC on Base). However, there is no OpenAPI spec, no request body schema, no response schema, and all documentation pages are empty beyond a wallet-connect prompt. The actual functionality behind the payment wall is unknown.

Warnings

  • No documentation available — docs, API, pricing, and README pages all show only 'Connect wallet'
  • No OpenAPI or request/response schema provided; impossible to know what the endpoint returns after payment
  • The endpoint path references a specific Stripe invoice ID (162); unclear if other IDs are supported
  • No examples of successful responses available

Citations

Provenance

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

Agent access