x402-gated card-transactions endpoint on Base, pay $0.02 per request in USDC.
What it does
This endpoint at lowpaymentfee.com exposes a card-transactions resource at `/api/v1/cards/39/transactions` behind an x402 payment wall. It is part of a broader platform that offers dozens of pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all priced at $0.02 per request settled in USDC on the Base network.
The specific endpoint listed here accepts HTTP POST requests and returns JSON. The x402 challenge confirms it is live, requiring a maximum payment of 20,000 base-unit USDC (i.e., $0.02, since USDC uses 6 decimals). Payment is made to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` using the USDC contract `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913` on Base. No API keys or rate limits are advertised; access is granted purely via the x402 payment header.
Documentation on the site is extremely thin — the docs, pricing, API, and README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI spec, no request/response schema, and no explanation of what the `/cards/39/transactions` resource actually returns or what POST body it expects. The endpoint's purpose (card transactions) can only be inferred from the URL path. Prospective callers should be aware that without documentation, integration requires experimentation or direct contact with the provider.
Capabilities
Use cases
- —Retrieving transaction data for a specific card via a single paid API call
- —Programmatic access to card transaction records without API key registration
- —Agent-driven financial data retrieval with per-request USDC micropayments
Fit
Best for
- —Developers wanting keyless, pay-per-use card transaction data
- —AI agents that can settle x402 payments on Base in USDC
- —Quick prototyping without subscription commitments
Not for
- —Production use requiring documented request/response schemas
- —High-volume batch processing where per-request fees add up
- —Users who cannot transact in USDC on the Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/cards/39/transactions \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>" \
-d '{}'Endpoint
Quality
The endpoint is confirmed live via a valid x402 402 challenge, but there is zero documentation on request format, response schema, or what the card-transactions resource actually provides. No OpenAPI spec, no examples, and all doc pages are empty. This is effectively a stub listing.
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 must guess the POST body format.
- —The purpose of /api/v1/cards/39/transactions is unclear — 'card transactions' is inferred solely from the URL path.
- —No OpenAPI or ai-plugin manifest found.
Citations
- —The endpoint returns a 402 challenge requiring 20,000 base-unit USDC ($0.02) on Base networkhttps://lowpaymentfee.com/api/v1/cards/39/transactions
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/cards/39/transactions
- —All APIs on the platform are priced at $0.02 per request with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com