x402basequality 0.30

Portfolio transactions endpoint on Base, paid per-call via x402 with USDC.

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

What it does

This endpoint at lowpaymentfee.com provides access to portfolio transaction data via a POST request to `/api/v1/portfolios/58/transactions`. It is part of a broader platform (lowpaymentfee.com) that offers a variety of pay-per-request APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all settled on the Base network using USDC via the x402 protocol.

The specific endpoint probed here charges a maximum of $0.02 per request (20,000 base units of USDC with 6 decimals). Payment is handled inline: callers attach an `X-PAYMENT` header conforming to x402 version 1, with the "exact" scheme on Base mainnet. The USDC asset contract is `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`. No API keys, rate limits, or upfront commitments are required — you pay per call.

Documentation is extremely sparse. The crawled docs, API, pricing, and README pages all returned only a "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no request/response examples, and no description of what fields the transactions endpoint accepts or returns. The endpoint is confirmed live (returns a proper 402 challenge), but without documentation it is difficult to know the expected POST body or the shape of the response. The platform's landing page lists this endpoint under "Finance & Web3" but the specific `/portfolios/58/transactions` path is not listed among the advertised APIs, suggesting it may be a specific portfolio resource rather than a general-purpose endpoint.

Capabilities

x402-paymentusdc-settlementbase-networkportfolio-transactionspay-per-requestno-api-key

Use cases

  • —Fetching transaction history for a specific portfolio
  • —Integrating portfolio transaction data into dashboards or analytics pipelines
  • —Agent-driven portfolio monitoring with per-call micropayments

Fit

Best for

  • —Developers wanting keyless, pay-per-use portfolio transaction access
  • —AI agents that can settle payments on Base via x402
  • —Projects needing low-friction access to financial transaction data without subscriptions

Not for

  • —Users who need detailed API documentation or OpenAPI specs before integrating
  • —High-volume batch transaction exports where per-call pricing adds up
  • —Anyone without a Base-compatible USDC wallet

Quick start

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

Endpoint

URLhttps://lowpaymentfee.com/api/v1/portfolios/58/transactions
Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is confirmed live via a valid 402 challenge, but there is no documentation, no OpenAPI schema, no request/response examples, and the specific portfolio endpoint isn't even listed on the site's landing page. Effectively a stub listing.

Warnings

  • —No API documentation available — docs, pricing, API, and README pages all return only a wallet-connect prompt
  • —No OpenAPI or request/response schema provided
  • —The specific path /api/v1/portfolios/58/transactions is not listed among the site's advertised APIs — it may be a hardcoded portfolio resource
  • —Cannot confirm what POST body fields are expected or what the response looks like

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-19 08:53:15Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-23

Agent access

JSONhttps://clawmart.sh/api/listings/F9Ffkh
Portfolio transactions endpoint on Base, paid per-call via x402 with USDC. — Clawmart · Clawmart