Retrieve portfolio holdings data via x402 micropayment on Base for $0.02 per request.
What it does
This endpoint at lowpaymentfee.com returns holdings data for portfolio ID 66. It is part of a broader platform offering various data, AI, finance, and utility APIs, all gated behind x402 micropayments settled in USDC on the Base network. Each request costs $0.02 (20,000 base units of USDC with 6 decimals).
The endpoint accepts POST requests and returns JSON. The x402 challenge is live and well-formed, advertising exact-scheme payment to a specified wallet address with a 300-second timeout. No API keys or rate limits are required — access is granted purely through per-call payment.
Documentation is extremely sparse. The /docs, /pricing, /api, and /README pages all resolve to a "Connect wallet" stub with no meaningful content. There is no OpenAPI spec, no request/response schema documentation, and no examples of what the holdings response actually contains. The endpoint path suggests it returns financial portfolio holdings, but the exact fields and structure are unknown.
Capabilities
Use cases
- —Fetching current holdings for a specific investment portfolio
- —Integrating portfolio data into dashboards or analytics tools
- —Agent-driven portfolio monitoring with per-call payment
Fit
Best for
- —Developers needing on-demand portfolio holdings without API key management
- —AI agents that can settle x402 payments on Base
- —Low-volume or sporadic access to portfolio data where per-call pricing is preferable
Not for
- —High-frequency polling where $0.02/request adds up quickly
- —Users who need detailed API documentation or schema guarantees before integrating
- —Accessing portfolios other than ID 66 (only this specific portfolio path is confirmed)
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/portfolios/66/holdings \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The x402 challenge is live and pricing is clear ($0.02/request in USDC on Base). However, there is no OpenAPI spec, no request/response schema, no documentation beyond a landing page listing, and no examples. The specific endpoint (portfolios/66/holdings) is not even mentioned on the site's landing page, making its purpose inferrable only from the URL path. Effectively a stub listing.
Warnings
- —No API documentation available — /docs, /pricing, /api, and /README all return only a 'Connect wallet' stub
- —No request or response schema provided; the structure of holdings data is unknown
- —This specific endpoint (portfolios/66/holdings) is not listed on the provider's landing page — it may be a demo or test portfolio
- —The platform lists many endpoints but none appear to have public documentation
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/portfolios/66/holdings
- —The platform advertises $0.02 per request pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —The USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/portfolios/66/holdings