x402basequality 0.30

x402-gated card-transactions endpoint on Base, pay-per-call with USDC.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com exposes a card transactions resource at `/api/v1/cards/61/transactions` behind an x402 payment challenge. It accepts HTTP POST requests and is settled on the Base network using USDC (contract 0x8335…2913). The per-request cost is 20,000 base units of USDC, which equals $0.02 (USDC uses 6 decimals). No API keys or rate limits are required; callers simply attach an X-PAYMENT header with a valid x402 payment proof.

The hosting provider, lowpaymentfee.com, advertises a broad catalog of pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all priced at $0.02 per request. However, this specific endpoint (`/api/v1/cards/61/transactions`) is labeled generically as "Premium API Access" and its exact functionality is not documented beyond the path structure, which suggests it relates to retrieving or creating transactions for a specific card (ID 61). No OpenAPI schema, request body examples, or response examples were found in the crawl.

Because the docs, pricing, and README pages all returned only a "Connect wallet" stub with no substantive content, the actual request/response contract for this endpoint remains unknown. Callers should treat this as an exploratory integration until more documentation surfaces.

Capabilities

x402-paymentusdc-settlementbase-networkpay-per-requestcard-transactionshttp-post

Use cases

  • Retrieving or posting transactions for a specific card resource via pay-per-call x402
  • Integrating card transaction data into agent workflows without API key management
  • Demonstrating x402 protocol payment flows on Base with USDC

Fit

Best for

  • Developers experimenting with x402 payment protocol on Base
  • Agents that need keyless, pay-per-call access to card transaction data
  • Low-volume, on-demand card transaction queries

Not for

  • Production workloads requiring documented request/response schemas
  • High-volume batch processing where per-call pricing is inefficient
  • Users who need detailed API documentation before integrating

Quick start

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

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), but there is no OpenAPI schema, no documented request/response format, and all doc pages returned only a wallet-connect stub. The specific purpose of this card-transactions endpoint is unclear.

Warnings

  • No API documentation available — docs, pricing, and README pages all return only a 'Connect wallet' stub
  • No request body schema or response schema documented for this endpoint
  • The endpoint path references a specific card ID (61), which may not be generalizable
  • The provider lists many API categories but none appear to have substantive documentation

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-19 03:05:11Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-24

Agent access

x402-gated card-transactions endpoint on Base, pay-per-call with USDC. — Clawmart · Clawmart