x402basequality 0.25

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

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com returns holdings data for portfolio ID 68. 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 priced at $0.02 per request and settled via x402 micropayments in USDC on the Base network.

The specific endpoint `/api/v1/portfolios/68/holdings` accepts POST requests and returns JSON. The x402 challenge confirms it is live, requiring a maximum payment of 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimals. Payment is made to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout. No API keys or rate limits are advertised; access is gated purely by the x402 payment header.

Documentation 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 spec, no request/response schema, 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. Without documentation it is unclear what request body fields are expected or what the response structure looks like.

Capabilities

portfolio-holdingsx402-paymentusdc-micropaymentbase-networkjson-apipay-per-request

Use cases

  • Fetching holdings data for a specific portfolio via a single micropayment
  • Integrating portfolio data into an agent workflow without API key management
  • Programmatic access to portfolio composition for analytics or dashboards

Fit

Best for

  • Agents or bots that need on-demand portfolio holdings without subscription commitments
  • Developers exploring x402 micropayment-gated APIs on Base
  • Low-volume, pay-as-you-go portfolio data retrieval

Not for

  • High-volume institutional data feeds requiring SLAs and documentation
  • Users who need detailed API documentation or schema guarantees before integrating
  • Accessing arbitrary portfolio IDs (this endpoint is hardcoded to portfolio 68)

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.25/ 1.00

The endpoint is live and returns a valid x402 challenge with clear pricing, but there is no documentation, no OpenAPI spec, no request/response schema, and no examples. The purpose of the endpoint is inferred only from the URL path. This is effectively a stub listing.

Warnings

  • No API documentation available — /docs, /pricing, /api, and /README pages all show only 'Connect wallet' with no content.
  • No OpenAPI or JSON schema for request or response bodies; callers cannot know what to send or expect back.
  • Endpoint is scoped to a single hardcoded portfolio ID (68); unclear if other portfolio IDs are available or how to discover them.
  • The broader platform lists many endpoints but none have documented schemas or examples.

Citations

Provenance

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

Agent access

Retrieve portfolio holdings data via x402 micropayment on Base for $0.02/request. — Clawmart · Clawmart