x402-gated card transactions endpoint on Base, pay $0.02 per request in USDC.
What it does
This endpoint at lowpaymentfee.com provides access to a card transactions resource at `/api/v1/cards/29/transactions` via the x402 payment protocol. The endpoint is live and returns a standard 402 challenge requiring payment in USDC on the Base network. The maximum amount required per call is 20,000 base units of USDC (6 decimals), which equals $0.02 USD per request.
The provider's landing page advertises a broad suite of APIs spanning data & analytics, AI & machine learning, finance & Web3, and infrastructure utilities — all priced at $0.02 per request with no API keys, no rate limits, and instant access. However, the specific endpoint being listed here (`/api/v1/cards/29/transactions`) is not explicitly described on the landing page among the advertised APIs, and its exact functionality is unclear. The title "Premium API Access" and the path suggest it relates to card transaction data (possibly retrieving or creating transactions for card ID 29), but no documentation, request schema, or response schema is available to confirm this.
Payment settles via the x402 "exact" scheme on Base to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` using USDC (`0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`). The endpoint accepts POST requests and has a payment timeout of 300 seconds. Documentation pages (/docs, /pricing, /api, /README) all returned only a "Connect wallet" prompt with no substantive content.
Capabilities
Use cases
- —Retrieving or submitting card transaction data via a pay-per-request model
- —Integrating card transaction lookups into agent workflows without API key management
- —Programmatic access to card-level transaction records settled in USDC on Base
Fit
Best for
- —Agents needing keyless, pay-per-call access to card transaction data
- —Developers who prefer crypto micropayments over subscription billing
- —x402-compatible clients on the Base network
Not for
- —Users who need detailed API documentation before integrating
- —High-volume use cases where per-request pricing may add up
- —Anyone needing non-USDC or non-Base payment options
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/cards/29/transactions \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-header>"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but there is no documentation, no request/response schema, and the specific endpoint path (/api/v1/cards/29/transactions) is not listed among the provider's advertised APIs. All doc pages return only 'Connect wallet' with no content. The purpose and functionality of this specific endpoint must be inferred from the URL path alone.
Warnings
- —No API documentation available — all doc pages return only 'Connect wallet'
- —This specific endpoint (/api/v1/cards/29/transactions) is not listed among the provider's advertised APIs on the landing page
- —No request or response schema provided; exact functionality is unknown
- —The hardcoded card ID '29' in the path suggests this may be a specific resource rather than a general-purpose endpoint
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/cards/29/transactions
- —The provider advertises $0.02 per request pricing with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —USDC contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/cards/29/transactions
- —Documentation pages (/docs, /pricing, /api, /README) returned only 'Connect wallet' with no substantive contenthttps://lowpaymentfee.com/docs