x402basequality 0.30

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

Price
0.02 USDC / call
Protocol
x402
Verified
no
Endpoint
https://lowpaymentfee.com/api/v1/stripe/invoices/164

What it does

This endpoint at lowpaymentfee.com exposes a Stripe invoice resource (`/api/v1/stripe/invoices/164`) behind an x402 payment challenge. It is part of a broader platform that offers dozens of pay-per-request API endpoints spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all gated via the x402 protocol on the Base network, settled in USDC.

The specific endpoint listed here costs $0.02 per request (20,000 base units of USDC with 6 decimals). Payment is made via the x402 `exact` scheme: callers include an `X-PAYMENT` header with a signed payment authorization, and the server fulfills the request once payment is verified. The payment is directed to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` on Base mainnet, using the USDC contract at `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`. The endpoint accepts POST requests and returns `application/json`.

Documentation is extremely sparse — the docs, pricing, API, and README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI schema, no request/response examples, and no description of what the Stripe invoice endpoint actually returns or what parameters it accepts. The platform advertises no API keys, no rate limits, and instant access, but the actual behavior of this specific invoice endpoint is undocumented beyond its title "Premium API Access."

Capabilities

x402-payment-gatingusdc-settlementbase-networkstripe-invoice-accesspay-per-requestno-api-key-required

Use cases

  • —Programmatically retrieving or interacting with a Stripe invoice via a single micropayment
  • —Integrating pay-per-request invoice data into an agent workflow without managing API keys
  • —Demonstrating x402 protocol payment flows on Base mainnet

Fit

Best for

  • —Developers experimenting with x402 payment-gated APIs
  • —Agents that need one-shot access to invoice data without subscription management
  • —Projects already using USDC on Base for micropayments

Not for

  • —Users who need detailed API documentation or guaranteed SLAs before integrating
  • —High-volume invoice processing where per-request costs add up quickly
  • —Anyone without a Base-compatible USDC wallet

Quick start

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

Endpoint

URLhttps://lowpaymentfee.com/api/v1/stripe/invoices/164
Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge with clear pricing, but there is zero documentation on request parameters, response schema, or what the endpoint actually does beyond the label 'Premium API Access'. Docs pages are empty. No OpenAPI spec or examples are available.

Warnings

  • —No documentation available — docs, pricing, API, and README pages all show only 'Connect wallet' with no content
  • —No request or response schema provided; callers cannot know what parameters to send or what data to expect
  • —The endpoint path references a specific Stripe invoice ID (164), which may be a demo or placeholder rather than a general-purpose API
  • —The platform lists many endpoints on its homepage but none have documented schemas or usage examples

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/K8hVWr
x402-gated Stripe invoice endpoint on Base, pay-per-call with USDC. — Clawmart · Clawmart