Retrieve portfolio holdings via x402 micropayment on Base for $0.02 per request.
What it does
This endpoint at lowpaymentfee.com returns holdings data for portfolio #32 via a POST request, gated by the x402 payment protocol. Each call costs $0.02 in USDC on the Base network — the x402 challenge advertises a maxAmountRequired of 20,000 base units of USDC (6 decimals), which equals $0.02. No API keys or rate limits are required; callers simply attach an X-PAYMENT header with a valid x402 payment proof.
The provider's landing page lists a broad catalog of pay-per-call APIs spanning data analytics, AI/ML inference, finance/crypto market data, and utility services, all priced at $0.02 per request. This specific endpoint falls under the finance/Web3 category and appears to serve portfolio holdings information, though the exact response schema is not documented. The endpoint accepts POST requests and returns application/json.
Documentation is extremely sparse — the /docs, /pricing, /api, and /README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI spec, no request/response schema, and no usage examples available from the crawl. The endpoint is confirmed live (returns a proper 402 challenge), but without documentation it is unclear what request body is expected or what the response payload looks like.
Capabilities
Use cases
- —Fetching current holdings for a specific portfolio programmatically
- —Integrating portfolio data into dashboards or trading bots
- —Querying holdings as part of an automated financial analysis pipeline
Fit
Best for
- —Agents or apps that need on-demand portfolio holdings without managing API keys
- —Developers experimenting with x402 micropayment-gated APIs
- —Low-volume, pay-as-you-go portfolio data retrieval
Not for
- —Users who need detailed API documentation or response schema guarantees before integrating
- —High-frequency bulk data retrieval where per-call pricing adds up quickly
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/portfolios/32/holdings \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-proof>"Endpoint
Quality
The endpoint is confirmed live with a valid x402 402 challenge, but there is zero documentation: no OpenAPI spec, no request/response schema, no examples. The docs pages are empty wallet-connect stubs. The purpose of the endpoint can only be inferred from the URL path.
Warnings
- —No API documentation available — /docs, /api, /pricing, and /README pages all return only a wallet connect prompt with no content.
- —No request body schema documented; it is unknown what POST body the endpoint expects.
- —No response schema or example response available; the actual data returned is unverified.
- —The endpoint serves portfolio #32 specifically; it is unclear whether other portfolio IDs are accessible or what portfolio #32 represents.
Citations
- —The x402 challenge advertises maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/portfolios/32/holdings
- —USDC asset address 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/portfolios/32/holdings
- —All APIs priced at $0.02 per request with no API keys, no rate limits, instant access on Base networkhttps://lowpaymentfee.com
- —The provider lists finance/Web3, AI/ML, data analytics, and infrastructure API categorieshttps://lowpaymentfee.com