x402basequality 0.30

Pay-per-call card transaction API on Base via x402, settled in USDC at $0.02/request.

Price
0.02 USDC / call
Protocol
x402
Verified
no
Endpoint
https://lowpaymentfee.com/api/v1/cards/100/transactions

What it does

This endpoint at lowpaymentfee.com exposes a card transactions resource at `/api/v1/cards/100/transactions` behind the x402 payment protocol. It accepts POST requests and requires an X-PAYMENT header carrying a valid x402 payment proof. The endpoint is live, returning a standard 402 challenge with an `exact` payment scheme on the Base network, settling in USDC (contract `0x8335…2913`) to the specified payTo address.

The maximum amount required per call is 20,000 base units of USDC (6 decimals), which equals $0.02 USD — consistent with the site-wide flat pricing of $0.02 per request. The provider advertises no API keys, no rate limits, and instant access. Payment timeout is 300 seconds.

The specific functionality of this particular endpoint (`/cards/100/transactions`) is not well-documented. The provider's landing page lists many API categories (data & analytics, AI/ML, finance, infrastructure) but does not explicitly list this cards/transactions path among them. The endpoint title is simply "Premium API Access," which is the generic description embedded in the x402 challenge. Without further documentation or example responses, the exact data returned by this endpoint remains unclear — it likely returns transaction data associated with card ID 100, but this is inferred from the URL structure alone.

Capabilities

x402-paymentusdc-settlementbase-networkpost-endpointcard-transactionspay-per-request

Use cases

  • —Retrieving transaction history for a specific card via a pay-per-call model
  • —Integrating card transaction data into agent workflows without API key management
  • —Programmatic access to financial card data settled on Base L2

Fit

Best for

  • —Agents needing on-demand card transaction data without subscription commitments
  • —Developers wanting x402-native payment integration on Base
  • —Low-volume or sporadic access patterns where per-call pricing is economical

Not for

  • —High-volume bulk transaction data retrieval where per-call costs add up
  • —Use cases requiring detailed API documentation and guaranteed SLAs
  • —Users who cannot settle payments in USDC on the Base network

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/cards/100/transactions \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <x402-payment-proof>"

Endpoint

URLhttps://lowpaymentfee.com/api/v1/cards/100/transactions
Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge, but there is no documentation, no OpenAPI schema, no example request/response, and the specific functionality of the /cards/100/transactions path is not described anywhere on the site. The docs, pricing, and API pages all render only a 'Connect wallet' prompt with no useful content.

Warnings

  • —No documentation available for this specific endpoint — its exact functionality is unknown
  • —The /cards/100/transactions path is not listed among the provider's advertised APIs on the landing page
  • —No request body schema or response schema is documented
  • —Docs, pricing, and API pages are empty (only show 'Connect wallet')
  • —Endpoint purpose is inferred solely from URL structure

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-19 02:50:20Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-24

Agent access

JSONhttps://clawmart.sh/api/listings/4CpMAp
Pay-per-call card transaction API on Base via x402, settled in USDC at $0.02/request. — Clawmart · Clawmart