Fund and ETF portfolio composition from N-PORT and N-MFP filings
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.
Not tested: has real-world effectsour last check, 2026-09-24
0 of 0checks answered this week
n/amedian answer time
$0.005listed price per call
n/aprice it asked us
Paid test badge: not yet. The checks above are free: we call the tool without paying and read the payment request it sends back. The Verified badge needs paid calls whose answers match the promised output, and nobody can buy a badge.
Endpoint
POST https://agent.pocket.network/v1/fund-etf-holdings
| Category | Everything else |
|---|---|
| Provider host | agent.pocket.network |
| Networks | eip155:8453 |
| Payment schemes | exact |
| Self-reported calls, 30 days | 4 from 2 payers (the provider's figure, not ours) |
Our checks, last 30 days
We never call tools that send, buy, move money or file anything, not even without paying.
Example input (from the provider)
{
"body": {
"query": "S&P 500"
},
"bodyType": "json",
"method": "POST",
"type": "http"
}
Promised output schema (from the provider)
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"input": {
"additionalProperties": false,
"properties": {
"body": {
"description": "A fund or ETF to look up.",
"properties": {
"query": {
"description": "Fund or ETF name to search, e.g. S&P 500.",
"type": "string"
}
},
"required": [
"query"
],
"type": "object"
},
"bodyType": {
"enum": [
"json",
"form-data",
"text"
],
"type": "string"
},
"method": {
"enum": [
"POST",
"PUT",
"PATCH"
],
"type": "string"
},
"type": {
"const": "http",
"type": "string"
}
},
"required": [
"type",
"method",
"bodyType",
"body"
],
"type": "object"
},
"output": {
"properties": {
"example": {
"properties": {
"data": {
"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.",
"type": "object"
},
"portal": {
"properties": {
"provenance": {
"const": "third-party-supplier"
},
"schemaCheck": {
"enum": [
"passed",
"undeclared",
"unchecked"
]
},
"serviceId": {
"const": "fund-etf-holdings"
}
},
"required": [
"provenance",
"serviceId",
"schemaCheck"
],
"type": "object"
}
},
"required": [
"portal",
"data"
],
"type": "object"
},
"type": {
"type": "string"
}
},
"required": [
"type"
],
"type": "object"
}
},
"required": [
"input"
],
"type": "object"
}