x402basequality 0.30

Retrieve portfolio holdings data via x402 micropayment on Base network for $0.02/request.

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

What it does

This endpoint at lowpaymentfee.com returns holdings data for portfolio ID 54. It is part of a broader platform (lowpaymentfee.com) that offers a variety of pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3, and infrastructure utilities — all gated behind the x402 payment protocol on the Base network using USDC.

The specific endpoint `/api/v1/portfolios/54/holdings` accepts POST requests and returns JSON. Payment is settled on-chain via USDC on Base (contract 0x8335…2913) with a maximum amount of 20,000 base units, which equals $0.02 (USDC uses 6 decimals). There are no API keys, no rate limits, and no signup required — callers simply attach an x402 payment header to each request. The x402 challenge is live and well-formed (version 1, scheme "exact").

Documentation on the site is extremely sparse: the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI schema, no request/response examples, and no description of what fields the holdings response contains or what parameters the POST body accepts. The endpoint appears to be part of a portfolio/finance domain, but without documentation the exact data returned is unknown.

Capabilities

x402-paymentusdc-baseportfolio-holdingspay-per-requestno-api-keyjson-response

Use cases

  • —Fetching holdings data for a specific portfolio via automated agent
  • —Integrating portfolio position data into a trading dashboard
  • —Programmatic access to portfolio composition without API key management

Fit

Best for

  • —Agents that need on-demand portfolio holdings without signup
  • —Developers experimenting with x402 micropayment-gated APIs
  • —Automated workflows requiring pay-per-call finance data

Not for

  • —Users needing detailed API documentation or schema guarantees before integration
  • —Bulk data retrieval where per-request pricing would be cost-prohibitive
  • —Users without a Base-network USDC wallet

Quick start

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

Endpoint

URLhttps://lowpaymentfee.com/api/v1/portfolios/54/holdings
Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The x402 challenge is live and pricing is clear ($0.02 USDC on Base), but there is zero documentation: no OpenAPI spec, no request/response schema, no examples, and all doc pages render only 'Connect wallet'. The purpose of this specific endpoint (portfolio 54 holdings) is only inferable from the URL path. Effectively a stub listing.

Warnings

  • —No API documentation available — all doc pages return only 'Connect wallet'
  • —No OpenAPI or request/response schema provided
  • —The endpoint is hardcoded to portfolio ID 54; unclear if other portfolio IDs are supported
  • —No examples of request body or response payload exist in crawled material

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-19 08:45:02Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-28

Agent access

JSONhttps://clawmart.sh/api/listings/dsgmbH
Retrieve portfolio holdings data via x402 micropayment on Base network for $0.02/request. — Clawmart · Clawmart