x402basequality 0.30

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 returns portfolio holdings data for portfolio ID 33. It is part of a broader platform offering various pay-per-request APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services. All endpoints on the platform use the x402 payment protocol, settling in USDC on the Base network.

The specific endpoint `/api/v1/portfolios/33/holdings` accepts POST requests and returns JSON. The x402 challenge advertises a maximum cost of 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 per request (USDC uses 6 decimals). No API keys or rate limits are required — payment is handled inline via the X-PAYMENT header per the x402 protocol. The payment timeout is 300 seconds.

Documentation on the platform is extremely sparse. The landing page lists available endpoints and pricing, but the /docs, /api, /pricing, and /README pages all render 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 holdings response contains. The endpoint is live (returns a proper 402 challenge), but the actual data returned after payment is unknown from available materials.

Capabilities

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

Use cases

  • Retrieve holdings data for a specific portfolio via micropayment
  • Integrate portfolio data into trading bots or dashboards without API key management
  • Pay-per-call access to financial portfolio information on Base network

Fit

Best for

  • Agents needing on-demand portfolio holdings without subscription commitments
  • Developers prototyping financial dashboards with instant API access
  • x402-compatible clients on the Base network

Not for

  • Users needing detailed API documentation or schema guarantees before integrating
  • Bulk data retrieval where per-request pricing becomes expensive
  • Accessing arbitrary portfolio IDs (this endpoint is hardcoded to portfolio 33)

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/portfolios/33/holdings \
  -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 and returns a valid x402 challenge with clear pricing ($0.02 USDC on Base). However, there is no documentation, no OpenAPI schema, no request/response examples, and no explanation of what data the holdings endpoint actually returns. The docs pages are all empty wallet-connect stubs. This is effectively a stub listing.

Warnings

  • No API documentation available — /docs, /api, /pricing, and /README all render only a wallet connect prompt
  • No OpenAPI or request/response schema provided; response format is completely unknown
  • Endpoint is scoped to a single portfolio ID (33); unclear if other portfolio IDs are available
  • Platform appears to be a generic demo or early-stage project with many listed endpoints but no substantive docs

Citations

Provenance

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

Agent access