Documentation

Use the sourced data model

Use browser search, API resources, MCP tools, recurring data feeds, and provenance conventions across the AUMSearch platform.

VERSION V1

SCHEMA JSON

SUPPORT SOURCE-FIRST

Search public records in the browser. API, MCP, and data-feed access use account credentials and the same source-linked record model described below.

Query language

Use explicit, URL-addressable filters

The browser stores its plain-text query and source-aware filters in the URL. The REST API uses the corresponding documented query parameters.

/search/?mode=advisers&q=Vanguard%20Group&state=PA
/search/?mode=holdings&q=594918104&cik=1067983
/v1/filings?form_type=13F-HR&source=sec_edgar
/v1/securities?query=Apple&sort=relevance

API quickstart

Make a read-only GET request

Choose a resource
Start with managers, filings, holdings, or securities.
Bound the query
Use identifiers, dates, filters, and keyset cursors instead of unbounded downloads.
Preserve provenance
Store source and filing identifiers with any downstream result.

curl "https://aumsearch.com/v1/managers?query=berkshire"

Registered funds & ETFs

Resolve the product before using the filing

Registered-fund records distinguish the legal registrant, fund series, share class, and filing. Use a CIK for the registrant, SEC series and class identifiers for the product, and the accession number for a specific submission.

Form N-1A describes the registration statement used by open-end funds.
485APOS, 485BPOS, and 485BXT identify different post-effective amendment paths.
Filing, effective, listing, and launch dates remain separate fields.
Normalized attributes retain the filing and document that reported them.

Read the Form 485 and N-1A data guide

Dataset guides

Start with the source contract

Each dataset guide documents what the public record means, representative normalized columns, useful joins, source cadence, amendments, research workflows, and interpretation limits. Use the guide before selecting API fields or defining a recurring feed.

Advisers, people, and private markets

Connect firms and representatives to their registrations, narrative disclosures, private funds, service providers, and exempt offerings.

Adviser firms and Form ADV recordsAdviser firms · Form ADV filings · ADV-W · Ownership · Disclosures
Form ADV Schedule D private fundsPrivate fund IDs · Fund types · Gross assets · Service providers · Form D links
Investment adviser representative recordsIndividual CRD · Firm history · State registrations · Qualifications · Disclosures
Form ADV Part 2 brochures and Form CRSPart 2A brochures · Part 2B supplements · Form CRS · Document versions · Extracted sections
Form D and D/A offering recordsForm D/D-A filings · Issuers · Offerings · Recipients · Amendments

Registered funds and portfolios

Move from a registrant and series to its registration lifecycle, portfolio holdings, share classes, and source filings.

Registered funds and Form 485 filingsForm N-1A · Form 485 · Series IDs · Class IDs · Prospectuses
Form N-PORT fund portfolio holdingsFund portfolios · Position values · Debt terms · Derivatives · Counterparties

Institutional holdings and securities

Study periodic holdings and the identifiers connecting managers, issuers, securities, filings, and fund portfolios.

Form 13F filings and reported holdingsForm 13F filings · Reported holdings · Managers · Report periods · Amendments
Securities and identifier historyCUSIP · Ticker · FIGI · Issuer · Security class

Data feeds

Receive source-linked data on a schedule

Data feeds deliver recurring full snapshots or bounded changes for the datasets and reporting periods included with your account. Every delivery retains source identifiers, dates, and provenance fields.

delivery: incremental
cadence: daily
format: jsonl
destination: customer-managed storage

x402 payments

Pay for compatible resources directly over HTTP

x402 lets compatible clients access selected pay-per-request resources without managing a conventional subscription or API key.

GET https://aumsearch.com/api/x402/demo
402 Payment Required
PAYMENT-REQUIRED: <base64 payment requirements>

GET https://aumsearch.com/api/x402/demo
PAYMENT-SIGNATURE: <base64 signed payment>

Payment requirements are returned with the resource response so compatible clients can inspect the network, asset, amount, and settlement terms before paying.

MCP quickstart

Remote server configuration

The read-only MCP endpoint uses Streamable HTTP on the primary domain. Request credentials, then add the endpoint to a compatible client.

{ "url": "https://aumsearch.com/mcp" }

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.

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.

A registered-fund amendment does not by itself prove that a product launched. Interpret the filing date, effective date, series and class status, listing, and commencement of sales as separate events.