DOCUMENTATION / 05
Build on sourced public data
Start with browser queries, move to API resources, or connect the same data model to an MCP client.
01 / QUERY LANGUAGE
Compose filters with familiar field syntax
Browser and API queries use the same conceptual fields. Combine exact matches, source filters, identifiers, and reporting periods.
manager_name:"Vanguard Group" AND form_type:"13F-HR"
ticker:MSFT AND period:2026Q1
source:ADV AND state:NY02 / API QUICKSTART
Send an authenticated GET request
- 1Request a key
Create a scoped credential for your application or research workflow.
- 2Choose a resource
Start with managers, filings, holdings, or securities.
- 3Preserve provenance
Store source and filing identifiers with any downstream result.
curl "https://api.aumsearch.com/v1/managers?query=berkshire" \
-H "Authorization: Bearer $AUMSEARCH_API_KEY"03 / MCP QUICKSTART
Add the remote server to your MCP client
Configure the HTTPS endpoint and bearer token, then inspect the exposed tools before giving an agent access.
{ "url": "https://mcp.aumsearch.com",
"headers": { "Authorization": "Bearer $AUMSEARCH_API_KEY" } }04 / PROVENANCE
Keep normalized answers tied to primary sources
Records expose source type, accession or registration identifiers, filed date, reporting period, retrieval timestamp, and source-document URL where available.
05 / DISCLOSURE LIMITS
Interpret filing data within its reporting rules
13F filings are delayed public disclosures of specified long-equity positions. They do not show a complete portfolio, real-time exposure, short positions, or every asset class.