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 17. 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 via the x402 payment protocol on the Base network.
The endpoint accepts POST requests and returns JSON. Payment is settled in USDC on Base (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) with a maximum amount of 20,000 base units, which equals $0.02 (USDC uses 6 decimals). The x402 challenge was successfully captured, confirming the endpoint is live. No API keys or rate limits are advertised; access is granted purely through per-request micropayment.
Documentation is extremely sparse. The crawled /docs, /api, /pricing, and /README pages all returned only a "Connect wallet" prompt with no additional technical content. There is no OpenAPI spec, no request/response schema, and no description of what fields the holdings response contains or what parameters the POST body expects. The endpoint path suggests it returns holdings for a specific portfolio (ID 17), but the exact data shape is unknown.
Capabilities
Use cases
- —Fetching holdings data for a specific portfolio via micropayment
- —Integrating portfolio data into agent workflows without API key management
- —Programmatic access to portfolio composition data on a per-request billing model
Fit
Best for
- —Agents needing on-demand portfolio holdings without subscription commitments
- —Developers exploring x402 micropayment-gated APIs on Base
- —Low-volume or sporadic portfolio data lookups
Not for
- —High-frequency bulk portfolio data retrieval (no documented batch endpoint)
- —Users who need detailed API documentation or guaranteed SLAs
- —Accessing arbitrary portfolio IDs (this endpoint is hardcoded to portfolio 17)
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/portfolios/17/holdings \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_header>"Endpoint
Quality
The x402 challenge is live and pricing is clear ($0.02 USDC on Base), but there is zero documentation on request parameters, response schema, or what data the endpoint actually returns. No OpenAPI spec, no examples, and all doc pages are empty wallet-connect stubs.
Warnings
- —No request body schema documented — unknown what POST parameters are accepted
- —No response schema documented — unknown what fields are returned
- —All documentation pages (/docs, /api, /pricing, /README) returned only 'Connect wallet' with no content
- —Endpoint is scoped to a single portfolio ID (17); unclear if other portfolio IDs are available
- —Platform appears to be a generic demo or early-stage site with many listed endpoints but no substantive docs
Citations
- —Endpoint returns 402 with x402 challenge advertising USDC on Base, maxAmountRequired 20000 base unitshttps://lowpaymentfee.com/api/v1/portfolios/17/holdings
- —Platform advertises $0.02 per request, no API keys, no rate limits, Base networkhttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/portfolios/17/holdings
- —Documentation pages /docs, /api, /pricing, /README contain only 'Connect wallet'https://lowpaymentfee.com/docs