x402basequality 0.30

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

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

What it does

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

The specific endpoint probed here returns an x402 challenge requesting payment of up to 20,000 base units of USDC (0x8335…2913 on Base). Since USDC uses 6 decimals, this translates to $0.02 per request, consistent with the site's advertised flat pricing of $0.02/request across all endpoints. Payment is made via the x402 exact scheme, meaning each call requires a one-shot micropayment in the `X-PAYMENT` header. No API keys, subscriptions, or rate limits are advertised — access is purely pay-per-use.

Documentation is extremely sparse. The landing page lists available endpoints with brief labels but provides no request/response schemas, parameter descriptions, or example payloads. The `/docs`, `/api`, `/pricing`, and `/README` pages all render only a "Connect wallet" prompt with no additional content. Because this specific endpoint path references a portfolio ID (60) and "transactions," it likely returns or creates transaction records for a given portfolio, but the exact input format and response structure are undocumented. Agents should expect to send a JSON POST body and receive a JSON response, but the precise fields are unknown.

Capabilities

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

Use cases

  • —Retrieving or creating transaction records for a specific portfolio
  • —Integrating pay-per-call financial data into agent workflows
  • —Accessing portfolio data without API key registration

Fit

Best for

  • —Agents that can settle x402 payments in USDC on Base
  • —Use cases requiring keyless, pay-per-request portfolio transaction access
  • —Developers exploring x402 protocol integrations

Not for

  • —Users who need detailed API documentation or response schemas before integrating
  • —High-volume batch processing where per-request fees add up quickly
  • —Anyone without a Base-compatible USDC wallet

Quick start

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

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge with clear pricing ($0.02 USDC on Base). However, there is no documentation, no request/response schema, no examples, and the purpose of this specific endpoint (portfolios/60/transactions) is only inferable from the URL path. The docs, pricing, and README pages are all empty beyond a wallet connect prompt.

Warnings

  • —No request or response schema is documented for this endpoint
  • —The portfolio ID '60' is hardcoded in the path — unclear if other portfolio IDs are valid
  • —All documentation pages (/docs, /api, /pricing, /README) render only 'Connect wallet' with no content
  • —The exact purpose of this endpoint (read vs. write transactions) is unknown

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-19 08:50:09Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-27

Agent access

JSONhttps://clawmart.sh/api/listings/q7JY5r
x402-gated portfolio transactions endpoint on Base, pay-per-call with USDC. — Clawmart · Clawmart