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 provides "Premium API Access" behind an x402 paywall. The specific resource `/api/v1/stripe/invoices/178` appears to be a Stripe invoice-related endpoint, though the exact functionality is not documented beyond the generic title. Payment is settled on the Base network using USDC (contract 0x8335…2913) via the x402 "exact" scheme.

The hosting site lowpaymentfee.com advertises a broad catalog of pay-per-call APIs spanning data analytics, AI/ML inference (sentiment, summarization, classification, embeddings), finance/crypto market data, and utility services. All listed endpoints share a uniform $0.02-per-request pricing model with no API keys, no rate limits, and no commitments. However, the specific invoice endpoint probed here advertises a maxAmountRequired of 20,000 base units of USDC (6 decimals), which equals $0.02 — consistent with the site-wide pricing.

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, and no usage examples. The endpoint is confirmed live (returns a valid x402 challenge with HTTP 402), but without documentation it is unclear what request body is expected or what the response payload looks like.

Capabilities

x402-paymentusdc-base-networkstripe-invoicespay-per-requestno-api-key

Use cases

  • Retrieving or interacting with Stripe invoice data via a single paid API call
  • Programmatic invoice access without traditional API key management
  • Agent-driven payment workflows where per-call USDC settlement is preferred

Fit

Best for

  • Developers wanting keyless, pay-per-use Stripe invoice access
  • AI agents that can settle x402 payments on Base in USDC
  • Prototyping micropayment-gated API workflows

Not for

  • Users needing detailed API documentation or OpenAPI specs before integrating
  • High-volume invoice processing where per-call fees add up
  • Anyone without a Base-compatible USDC wallet

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/stripe/invoices/178 \
  -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 and returns a valid x402 challenge, but documentation is essentially nonexistent — all doc pages show only 'Connect wallet'. No OpenAPI spec, no request/response schemas, and no examples are available. The specific purpose of the /stripe/invoices/178 resource is unclear beyond the generic 'Premium API Access' label.

Warnings

  • No documentation available — all doc/pricing/README pages render only a wallet-connect prompt
  • No OpenAPI or request/response schema provided; request body format is unknown
  • The endpoint path references a specific invoice ID (178), which may be a demo or placeholder resource
  • The broader site lists many API categories but none have documented schemas or examples

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-19 10:20:41Z · 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