x402basequality 0.30

Pay-per-call portfolio transactions endpoint on Base via x402 (USDC, $0.02/request).

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This x402-enabled endpoint at lowpaymentfee.com provides access to portfolio transaction data via a POST request to `/api/v1/portfolios/47/transactions`. It is part of a broader platform offering data & analytics, AI/ML inference, finance/Web3, and infrastructure utility APIs, all priced at $0.02 per request with no API keys, no rate limits, and no commitments required.

Payment is settled on the Base network using USDC (contract `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`). The x402 challenge advertises a `maxAmountRequired` of 20000 base units, which at 6 decimals equals $0.02 per call. The endpoint uses the "exact" payment scheme with a 300-second timeout. No OpenAPI schema, detailed documentation, or example request/response bodies were found during crawling — the docs, pricing, API, and README pages all returned only a "Connect wallet" prompt with no substantive content.

Because this specific endpoint path references a hardcoded portfolio ID (47), it is unclear whether the endpoint is meant to be used generically or is specific to a single portfolio. The lack of input/output schema documentation makes it difficult to determine what fields the POST body should contain or what the response looks like. Agents should treat this as a stub-level listing until more documentation surfaces.

Capabilities

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

Use cases

  • Fetching transaction records 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 x402 payments on Base
  • Prototyping financial data integrations without subscription commitments

Not for

  • Production use requiring documented request/response schemas
  • Bulk historical transaction exports (no batch endpoint documented)
  • Users who cannot settle USDC payments on the Base network

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live (402 challenge captured) and pricing is clear ($0.02/request in USDC on Base), but there is no OpenAPI schema, no request/response examples, and all documentation pages returned only a wallet-connect prompt. The hardcoded portfolio ID and absent input/output schemas make practical use highly uncertain.

Warnings

  • No OpenAPI or input/output schema available — request body format is unknown
  • All documentation pages (docs, pricing, API, README) returned only 'Connect wallet' with no content
  • Endpoint path contains a hardcoded portfolio ID (47); unclear if this generalizes
  • No example responses available to verify what data is returned

Citations

Provenance

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

Agent access