> ## Documentation Index
> Fetch the complete documentation index at: https://docs.effectiveai.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Research a carrier or MGA

> Resolve directory identities, select filing filters, and keep company and group evidence distinct.

Use this workflow to answer a question such as “Which Texas homeowners filings
did this carrier submit during 2025?” Start with [connection setup](/guides/index#connect-once).

## Select the directory identity

Search by name, alias, or NAIC code with [List carriers](/api-reference/carriers/list-carriers):

```http theme={null}
GET /api/v2/carriers?q=Travelers&limit=20
```

Several legal entities can match a brand. Inspect the returned names and group
membership, follow `nextCursor` if needed, and select the entity that matches the
question. Use its returned `id` to inspect its aliases, group
members, and MGA relationships:

```http theme={null}
GET /api/v2/carriers/{carrierId}
```

Carrier domicile is not the state of a filing. The directory's `state` and `toi`
filters describe SERFF activity in the last 12 months; they do not enumerate all
historical activity. For a historical question, resolve identity first and put
the required dates on the filing query.

To investigate an entire group, use a returned `group.id` as the Filing `group`
filter. This broadens the question beyond one carrier. Do not substitute a group
because a carrier query returned few results.

## Find the carrier's filings

This example selects Texas homeowners filings submitted during the inclusive
2025 calendar year. Homeowners uses normalized TOI `04.0`; confirm the returned
classification fits the question. Change the dates explicitly for a different
research window.

```http theme={null}
GET /api/v2/filings?carrier={carrierId}&state=TX&toi=04.0&submissionDateFrom=2025-01-01&submissionDateTo=2025-12-31
```

Continue with the same filters and limit using [pagination and recovery](/guides/pagination-and-recovery).
An empty result does not justify silently changing the carrier, state, or dates.
Explain any broader follow-up query and keep its results distinct.

A filing's displayed `companyName` can name a different participating company
while `carrierIds` includes the selected carrier. That is an association, not
proof that the displayed company is an alias. A filing-level rate aggregate must
not be attributed entirely to one carrier in a multi-company filing. Directory
financials also have their own reporting year and scope; they are not filing-level
premium or state-and-line totals.

## Start from an MGA instead

Search for the MGA's name or alias:

```http theme={null}
GET /api/v2/mgas?q={name}&limit=20
```

Select an MGA and inspect its [detail](/api-reference/mgas/get-an-mga). Its returned
`carriers` describe links with roles and optional source notes. Use the linked
carrier IDs to discover candidate filings with the workflow above. A carrier
relationship does not establish that every filing by that carrier belongs to the
MGA; verify the program or MGA in filing descriptions and source documents.

There is no public Filing `mga` filter. Empty links mean no links were returned
from the directory, not proof that the MGA has no carrier relationships.

## Produce a supported answer

Inspect selected Filing IDs through [filing detail](/api-reference/filings/get-a-catalog-filing),
then [forms and rate impact](/guides/filing-research-data) or
[source documents](/guides/read-filing-documents). Report which identity and date
window you selected, the native filing references, and the evidence you actually
read. State when you stopped after a sample rather than exhausting pagination.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.