Fund and ETF portfolio composition from N-PORT and N-MFP filings. POST /v1/fund with a {query} naming a fund and get its filings and holdings as one JSON object. Deterministic per filing cycle. Pay per request in USDC; no account, no API key.
POST https://test.agent.pocket.network/v1/fund-etf-holdingsThe first call returns 402 Payment Required with the terms. Sign for those terms and retry the same request with the payment attached.
Derived from the published request schema.
curl -X POST https://test.agent.pocket.network/v1/fund-etf-holdings \
-H 'content-type: application/json' \
-d '{"query":"S&P"}'This service declares its response shape in prose rather than as fields, so there is nothing more specific to sample.
{}Make one real paid call from your own wallet — about $0.005 on Base Sepolia (eip155:84532). The wallet signs; nothing here holds a key. You'll see exactly what the service answers.
Methods the registry lists for this service. The portal forwards any call as sent; the supplier decides what it answers, and a delivered answer is settled.
| Method | Effect |
|---|---|
GET /v1/health | read |
GET /v1/version | read |
POST /v1/fund | read |
Published by the service itself. The example above is generated from these.
{
"type": "object",
"description": "A fund or ETF to look up.",
"properties": {
"query": {
"type": "string",
"description": "Fund or ETF name to search, e.g. S&P 500."
}
},
"required": [
"query"
]
}{
"type": "object",
"description": "For POST /v1/fund, a JSON object whose `filings` array carries the fund's portfolio holdings. The exact shape is the service's own and is not pinned here; errors return a JSON object with an `error` field, and the GET routes return their own small JSON documents."
}Request body used in the example: {
"query": "S&P"
}