x402basequality 0.30

Portfolio holdings data via x402 micropayment on Base network, $0.02 per request.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com returns portfolio holdings data for a specific portfolio (ID 40) behind an x402 paywall. 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 and settled in USDC on the Base network.

The endpoint accepts POST requests and returns JSON. Payment is handled via the x402 protocol: callers must include an X-PAYMENT header with a valid payment proof. The x402 challenge specifies an exact-scheme payment of up to 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimals. No API keys, rate limits, or subscriptions are required — each call is independently paid.

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 spec, no request/response schema, and no explanation of what fields the holdings response contains or what POST body (if any) is expected. The endpoint is live (402 challenge confirmed), but without documentation it is difficult to know exactly what data is returned or what input parameters are supported.

Capabilities

x402-paymentusdc-baseportfolio-holdingsjson-apimicropaymentpay-per-request

Use cases

  • Retrieving holdings data for portfolio #40 programmatically
  • Integrating portfolio data into dashboards or trading bots
  • Agent-driven portfolio analysis with per-call micropayments

Fit

Best for

  • Developers needing on-demand portfolio holdings without subscriptions
  • AI agents that can settle x402 payments on Base
  • Low-volume or sporadic access to portfolio data at $0.02/call

Not for

  • High-frequency bulk data retrieval (no documented batch endpoint)
  • Users who need detailed API documentation or schema guarantees before integrating
  • Accessing arbitrary portfolio IDs (this endpoint is scoped to portfolio 40)

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge with clear pricing, but there is no OpenAPI spec, no request/response schema, and all documentation pages are empty stubs showing only 'Connect wallet'. The specific purpose of portfolio 40 holdings is undocumented.

Warnings

  • No API documentation available — /docs, /api, /pricing, and /README all return only a wallet-connect prompt
  • No request body schema or response schema documented; callers must discover behavior empirically
  • Endpoint is scoped to a single portfolio ID (40); unclear if other portfolio IDs are available
  • The platform lists many other endpoints on its homepage but this specific holdings endpoint is not among them

Citations

Provenance

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

Agent access

Portfolio holdings data via x402 micropayment on Base network, $0.02 per request. — Clawmart · Clawmart