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 a specific portfolio (ID 21) via the x402 payment protocol. It accepts POST requests and is gated behind a per-call USDC micropayment on the Base network. The x402 challenge confirms the endpoint is live and requires a maximum of 20,000 base units of USDC (0.02 USD) per request, settled to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3.
The provider, lowpaymentfee.com, hosts a broader suite of APIs spanning data analytics, AI/ML inference, finance/Web3 data, and utility services — all priced at $0.02 per request with no API keys, no rate limits, and no minimum commitments. However, the specific endpoint being listed here (/api/v1/portfolios/21/holdings) is not documented on the provider's landing page among the advertised API categories, and no detailed schema or example response is available for it. The output MIME type is application/json, but the structure of the holdings response is unknown.
Because documentation is minimal — the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no further content — the actual data returned by this endpoint cannot be confirmed. Buyers should expect a JSON payload presumably containing portfolio holding details, but should verify the response structure before relying on it in production.
Capabilities
Use cases
- —Retrieving holdings data for portfolio #21 in a pay-per-call model
- —Integrating portfolio data into an agent workflow without API key management
- —Querying financial holdings with instant USDC micropayments on Base
Fit
Best for
- —Agents or bots that need on-demand portfolio holdings without subscription overhead
- —Developers experimenting with x402 payment-gated APIs
- —Low-volume, pay-as-you-go access to portfolio data
Not for
- —High-volume bulk portfolio data retrieval (no documented batch endpoint)
- —Users who need detailed API documentation or guaranteed response schemas before integration
- —Accessing portfolios other than ID 21 (only this specific resource is confirmed live)
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/portfolios/21/holdings \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_token>"Example
Request
{
"url": "https://lowpaymentfee.com/api/v1/portfolios/21/holdings",
"method": "POST",
"headers": {
"X-PAYMENT": "<x402_payment_token>",
"Content-Type": "application/json"
}
}Endpoint
Quality
The endpoint is confirmed live via a valid 402 challenge with clear pricing (0.02 USDC on Base). However, there is no documentation, no response schema, no example responses, and the specific portfolio holdings endpoint is not listed among the provider's advertised APIs. The docs/pricing/README pages are all empty beyond a wallet connect prompt.
Warnings
- —The /api/v1/portfolios/21/holdings endpoint is not listed among the provider's advertised APIs on the landing page — its purpose and data source are unverified.
- —No response schema or example response is available; the structure of the returned JSON is unknown.
- —All documentation pages (docs, API, pricing, README) render only a 'Connect wallet' prompt with no substantive content.
- —This endpoint is hardcoded to portfolio ID 21; it is unclear whether other portfolio IDs are supported.
Citations
- —The x402 challenge returns maxAmountRequired of 20000 base units of USDC (asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Base networkhttps://lowpaymentfee.com/api/v1/portfolios/21/holdings
- —The provider advertises $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —The provider lists APIs in categories: Data & Analytics, AI & Machine Learning, Finance & Web3, and Infrastructurehttps://lowpaymentfee.com