Portfolio holdings data via x402 micropayment on Base network, $0.02 per request.
What it does
This endpoint at lowpaymentfee.com returns portfolio holdings data for portfolio ID 62. It is part of a broader platform offering various paid API endpoints across data analytics, AI/ML, finance, and infrastructure categories, all settled via the x402 protocol on the Base network using USDC.
The endpoint accepts POST requests and returns JSON. Payment is handled inline via the x402 protocol: callers include an X-PAYMENT header with a signed USDC payment on Base. The maximum amount required per call is 20,000 base units of USDC (0.02 USD, since USDC uses 6 decimals). There are no API keys, no rate limits, and no subscription commitments — each request is independently paid.
The specific endpoint path (`/api/v1/portfolios/62/holdings`) suggests it returns the current holdings of a particular portfolio (ID 62). However, no documentation beyond the landing page is available — the docs, API, pricing, and README pages all resolve to a wallet-connect prompt with no substantive content. There is no OpenAPI schema, no request/response examples, and no description of what fields the holdings response contains or what POST body (if any) is expected. The endpoint is confirmed live (returns a valid 402 challenge).
Capabilities
Use cases
- —Retrieving current holdings for a specific portfolio
- —Integrating portfolio data into dashboards or trading bots
- —Agent-driven portfolio monitoring with per-request payment
Fit
Best for
- —Agents needing on-demand portfolio holdings without API key management
- —Developers who want pay-per-call access to portfolio data on Base
- —Automated workflows that need frictionless micropayment-gated data
Not for
- —Users needing detailed API documentation or schema guarantees before integrating
- —Bulk data retrieval where per-request costs would accumulate significantly
- —Anyone requiring holdings for arbitrary portfolio IDs (this endpoint is fixed to portfolio 62)
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/portfolios/62/holdings \
-H "X-PAYMENT: <x402-payment-header>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge with clear pricing. However, there is no OpenAPI schema, no request/response examples, and no meaningful documentation — docs pages all resolve to a wallet-connect stub. The purpose of this specific endpoint (portfolio 62 holdings) is only inferable from the URL path.
Warnings
- —No API documentation available — all doc pages return only a wallet-connect prompt
- —No request body schema or response schema provided
- —Endpoint is hardcoded to portfolio ID 62; unclear if other portfolio IDs are accessible
- —No OpenAPI spec or ai-plugin manifest found
Citations
- —The endpoint returns a 402 challenge requiring 20,000 base units of USDC on Base (0.02 USD per request)https://lowpaymentfee.com/api/v1/portfolios/62/holdings
- —The platform advertises $0.02 per request with no API keys, no rate limits, and instant access on the Base networkhttps://lowpaymentfee.com
- —USDC asset contract on Base: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/portfolios/62/holdings