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 18. 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 market data, and infrastructure utilities — all priced at $0.02 per request and settled via x402 micropayments in USDC on the Base network.
The specific endpoint `/api/v1/portfolios/18/holdings` accepts POST requests and returns JSON. Payment is handled inline via the x402 protocol: callers attach an `X-PAYMENT` header containing a signed USDC payment of up to 20,000 base units ($0.02, since USDC uses 6 decimals) to the payee address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` on Base. No API keys, accounts, or rate limits are required — access is granted per-payment.
Documentation on the site is extremely sparse. The docs, pricing, API, and README pages all render only a "Connect wallet" prompt with no additional 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 is confirmed live (returns a proper 402 challenge), but the lack of documentation means callers will need to experiment or contact the provider to understand the expected request format and response structure.
Capabilities
Use cases
- —Fetching holdings data for a specific investment portfolio on demand
- —Integrating portfolio position data into trading bots or dashboards
- —Agent-driven portfolio analysis with per-call payment
Fit
Best for
- —Developers needing on-demand portfolio holdings without API key management
- —AI agents that can settle x402 micropayments on Base
- —Low-volume or sporadic access to portfolio data at $0.02/call
Not for
- —High-frequency bulk data retrieval where per-call costs add up
- —Users who need detailed API documentation or guaranteed SLAs before integrating
- —Non-crypto-native callers who cannot produce x402 payment headers
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/portfolios/18/holdings \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <signed-x402-payment-header>"Endpoint
Quality
The endpoint is confirmed live with a valid x402 402 challenge, but there is zero documentation on request parameters, response schema, or what 'portfolio 18 holdings' actually contains. No OpenAPI spec, no examples, and all doc pages are empty. 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 request body schema or response schema documented; callers must guess or reverse-engineer the expected format
- —The endpoint is for a specific portfolio ID (18); it is unclear whether other portfolio IDs are available or what this portfolio represents
- —No OpenAPI or machine-readable schema provided by the server
Citations
- —The endpoint returns a 402 challenge requesting up to 20,000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/portfolios/18/holdings
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/portfolios/18/holdings
- —All endpoints on the platform are priced at $0.02 per request with no API keys or rate limitshttps://lowpaymentfee.com
- —The platform offers APIs across data/analytics, AI/ML, finance/Web3, and infrastructure categorieshttps://lowpaymentfee.com