x402basequality 0.35

Portfolio holdings data via x402 micropayment on Base network for $0.02/request

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com provides access to portfolio holdings data (portfolio ID 98) through the x402 payment protocol. It accepts POST requests and returns JSON. Payment is settled in USDC on the Base network at $0.02 per request (maxAmountRequired of 20,000 base units with 6 decimals = $0.02). No API keys or rate limits are required; access is granted per-call via the x402 payment header.

The endpoint is part of a broader platform (lowpaymentfee.com) that offers numerous pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all priced at $0.02 per request. However, this specific endpoint (/api/v1/portfolios/98/holdings) is not listed on the provider's landing page among the advertised API categories. Its exact response schema and the nature of the portfolio holdings data it returns are undocumented.

The x402 challenge was successfully captured (HTTP 402 with valid accepts block), confirming the endpoint is live. The payment address is 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 and the USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 (Base mainnet USDC). The timeout for payment settlement is 300 seconds.

Capabilities

x402-paymentusdc-baseportfolio-holdingspay-per-requestjson-apino-api-key

Use cases

  • Retrieving portfolio holdings data for portfolio analysis or dashboards
  • Programmatic access to holdings without managing API keys or subscriptions
  • Agent-driven portfolio monitoring with per-call micropayments

Fit

Best for

  • Agents or apps needing on-demand portfolio holdings data
  • Developers who prefer pay-per-call over subscription billing
  • Use cases requiring keyless, permissionless API access on Base

Not for

  • Users needing bulk/batch portfolio data at high volume (no documented batch endpoint)
  • Anyone requiring detailed API documentation or response schema guarantees before integrating

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/portfolios/98/holdings \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <x402_payment_token>"

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.35/ 1.00

The x402 challenge is live and pricing is clear ($0.02 USDC on Base), but there is no documentation for this specific endpoint — no request body schema, no response schema, and the endpoint is not listed among the provider's advertised APIs. The crawled docs/pricing/API pages returned only 'Connect wallet' with no useful content.

Warnings

  • This specific endpoint (/api/v1/portfolios/98/holdings) is not listed among the provider's advertised APIs on the landing page — its purpose and data source are unclear.
  • No request or response schema is documented; the output format must be discovered empirically.
  • Documentation pages (/docs, /api, /pricing, /README) returned no meaningful content beyond 'Connect wallet'.
  • The portfolio ID (98) is hardcoded in the URL; it is unknown whether other portfolio IDs are available or what data this portfolio represents.

Citations

Provenance

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

Agent access