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/81/holdings

What it does

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

The specific endpoint `/api/v1/portfolios/81/holdings` accepts POST requests and returns JSON. Payment is settled on-chain via USDC on Base (contract 0x8335…2913) with a maximum cost of 20,000 base units, which equals $0.02 (USDC uses 6 decimals). No API keys or rate limits are advertised; access is granted per-request upon valid x402 payment. The x402 challenge was confirmed live, returning a well-formed 402 response with version 1 of the protocol.

Documentation beyond the landing page is extremely thin — the /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI spec, no request/response schema documentation, and no example payloads available. The endpoint's purpose (portfolio holdings) is inferred solely from the URL path and the generic "Premium API Access" description. The actual request body format and response structure are unknown.

Capabilities

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

Use cases

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

Fit

Best for

  • —Agents that need on-demand portfolio holdings data with crypto micropayments
  • —Developers experimenting with x402 pay-per-call APIs on Base
  • —Use cases where avoiding API key registration is preferred

Not for

  • —Users who need detailed API documentation or guaranteed SLA before integrating
  • —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/81/holdings \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <x402-payment-token>"

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge, but there is no OpenAPI spec, no request/response schema, no documentation beyond a landing page, and no examples. The actual data returned is entirely unknown; even the endpoint's purpose is inferred only from the URL path.

Warnings

  • —No OpenAPI or schema documentation available — request body format and response structure are completely unknown
  • —All documentation pages (/docs, /api, /pricing, /README) render only a 'Connect wallet' prompt with no technical content
  • —The endpoint path references a specific portfolio ID (81); it is unclear whether other portfolio IDs are accessible or what this portfolio represents
  • —The platform lists many endpoints but provides no verifiable evidence of what data they actually return

Citations

Provenance

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

Agent access

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