Docs

Three ways in: the web app for people, the REST API for systems, and an MCP server for agents. They read the same data through the same contracts, so a field means the same thing whichever one you use.

The web app

Filters

The bar at the top carries the filters most searches need. All filters opens the full set — every field, grouped, with a search box over them — and shows a running count of matching plans as you go.

Location

Type a city or an address and press Enter, then choose a radius from 5 to 100 miles. Searches using a radius cover at most three filing years at a time.

Results

List or cards, your own column set and order, sort on any of 50 sortable fields, and totals across the whole filtered set rather than the visible page.

Sharing a search

The entire search lives in the URL. Copy the address bar and whoever opens it sees the same filters, columns, sort and page — no account needed to look.

Plan detail

Overview, trends across every year the plan appears, the full filing history including amendments, and the documents tab, which renders a filing back onto its official DOL form.

What Restricted hides

Without an account, identity fields are masked and pages cap at 25 rows. Every financial figure stays visible, and a banner says so rather than leaving you to wonder.

The REST API

An OpenAPI description is served at /docs on the API host, with every endpoint, request shape and response shape generated from the same contracts the web app uses. Authenticate with a bearer token; an unauthenticated caller is answered as Restricted rather than refused.

The endpoints most callers need.
Endpoint	What it returns
`POST /v1/search/plans`	A page of filings, plus totals across the whole match
`GET /v1/catalog/fields`	Every field, its type, operators and which years report it
`GET /v1/plans/:id`	One filing in full, with its fee benchmark
`GET /v1/plans/:id/trends`	One series per metric across every year the plan filed
`GET /v1/plans/:id/filings`	Filing history, amendments included
`GET /v1/codes/:kind`	State, entity type, NAICS and plan characteristic lookups
`GET /v1/stats`	What the corpus holds, by filing year. No account needed — the same figures the corpus page shows

Agents (MCP)

Point an MCP-compatible client at the remote server and it gains the tools below. The server never touches the database — it calls the same API you would, with your credentials and your entitlements, so an agent can never see more than you can.

The tools an MCP client sees.
Tool	What it does
`search_plans`	Run a search and get filings back
`export_search`	Export a search, in the shapes the catalog publishes
`benchmark_plan`	Benchmark a plan against its peer group
`get_service_providers`	Schedule C service providers for one filing
`get_field_catalog`	Discover what can be filtered and how
`get_plan`	One filing in full
`get_plan_trends`	A plan’s metrics across its filing years
`get_plan_filings`	A plan’s filing history
`get_related_plans`	Other plans under the same sponsor EIN
`lookup_codes`	Resolve a state, industry or characteristic code
`explain_fee_model`	Explain how a benchmark was reached

Agent access is included with Pro and above. A local stdio shim is available for clients that cannot reach a remote server.