x402basequality 0.25

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/1/transactions` via the x402 payment protocol. It accepts POST requests and is gated behind a per-call USDC payment on the Base network. The x402 challenge indicates a maximum cost of 20,000 base units of USDC (0x8335…), which with 6 decimals equals $0.02 per request. The provider describes it simply as "Premium API Access."

The broader lowpaymentfee.com platform advertises a suite of pay-per-request APIs spanning data analytics, AI/ML inference (sentiment, summarization, classification, embeddings), finance/crypto market data, and infrastructure utilities — all priced at $0.02 per call with no API keys, no rate limits, and no commitments. However, the specific `/api/v1/cards/1/transactions` endpoint is not listed among the publicly advertised APIs on the landing page, and no documentation, request schema, or response schema is available for it. The docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no further content.

Because there is no OpenAPI spec, no request/response examples, and no documentation beyond the endpoint title, it is unclear what data this endpoint returns or what input it expects. The endpoint is confirmed live (returns a valid x402 402 challenge), but its actual functionality remains opaque.

Capabilities

x402-paymentusdc-paymentbase-networkcard-transactionspay-per-callno-api-key

Use cases

  • Retrieving card transaction data on a per-call payment basis
  • Integrating card transaction lookups into agent workflows without API key management
  • Paying for financial data access with USDC on Base

Fit

Best for

  • Agents that need card transaction data and can pay with USDC on Base
  • Developers wanting keyless, pay-per-use financial API access
  • Prototyping x402 payment flows against a live endpoint

Not for

  • Production use cases requiring documented request/response schemas
  • Users who need free or subscription-based access rather than per-call crypto payments
  • Anyone needing detailed API documentation before integration

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/cards/1/transactions
# Returns 402 with x402 challenge; attach X-PAYMENT header with valid USDC payment on Base to access.

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.25/ 1.00

The endpoint is live and returns a valid x402 challenge, but there is no documentation, no request/response schema, no examples, and the specific endpoint is not even listed on the provider's own landing page. Functionality is entirely opaque.

Warnings

  • No documentation available — docs, API, pricing, and README pages all show only 'Connect wallet' with no content.
  • The /api/v1/cards/1/transactions endpoint is not listed among the provider's publicly advertised APIs.
  • No request or response schema is provided; it is unknown what input the endpoint expects or what it returns.
  • The endpoint name suggests financial card transaction data, which may fall under regulated financial data categories.

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-19 02:50:24Z · 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