← Plugin catalog
Business & Operations

Effective

Effective AI, Inc. v1.0.1

Insurance filings and rates

Create a free account to save this plugin.

From the developer

Declared capabilities

  • See competitor rate and form changes with the filing behind them
  • Review the assumptions and sources behind a rate change
  • Compare coverage wording, exclusions and endorsements

Cost & access

Effective does not sell products or process payments in ChatGPT or Codex.

Declared limitations

  • Request unrelated to Effective: writes the reply without calling any Effective tools.
  • Submitting to a regulator, which Effective can't do: explains that Effective prepares filing workspaces but doesn't submit filings to regulators, and makes no change.
  • Bulk delete without a specific target: does not call mutate; asks the user to name specific filings and confirm before deleting anything.

Onboarding example

Which competitors filed homeowners rate changes in Texas this year? Show the filing behind each one.
Sources & dates

Developer declarations; not independently tested. Listing last checked Nov 6, 2026. Package observed Nov 6, 2026.

View package source →

Description

From the marketplace listing

Ask about insurance carriers, products and regulatory filings, and get answers backed by the filings and source documents in Effective. With the Effective plugin you can: - Find competitors' rate, rule and form filings for a line of business and state, with the filing behind each change. - Compare filed rate changes, including the indicated and selected changes, and tell filed, approved and effective changes apart. - Review the actuarial support for a rate change: assumptions, exhibits and data gaps. - Compare coverage wording, exclusions, endorsements and form editions across filings. - Benchmark a carrier's premium and underwriting results from its annual financials. - Create and update working filings and organize their rate, rule, form and supporting documents. - Check whether a filing is ready, review objection letters, draft responses and comment on them.

Language: English · Automatically detected from descriptions.

Matches for “paris”

Exact text from the indicated source. A mention alone does not establish support for your task.

Publisher keywords · listing

insurance competitive-intelligence regulatory-research actuarial rate-filings coverage-comparison filing-preparation

What changed

Keywords

Files & skills

File archives

Plugin package5 files · 6.55 KBBrowse files →
Skill instructions
effective6.95 KB

View saved version →

---
name: effective
description: Use Effective when insurance teams ask to find or compare competitor filings, review coverage wording or rate changes, examine actuarial support or carrier financials, prepare or update filing workspaces, organize filing documents, comment on objections, or check filing readiness. Recognize insurance terms such as line of business, rate/rule schedule, form edition, actuarial memo, and objection letter.
---

# Effective

Use the Effective MCP connector to find evidence and work with the user's Effective data.

## Choose an endpoint

Use either approach:

- Call `discover` with a `query` describing the information or action requested. Add `intent` when the purpose helps choose the right endpoint or response fields. It returns up to three Markdown steps, each with the HTTP method, effective:// URI, a reason and parameter hints. Resolve each step's Needs, note any Not supported line, and use inspect for exact inputs. Steps describe possible calls; they are not results.
- Read the API documentation at https://docs.effectiveai.app/llms.txt to choose an endpoint directly.

Use `inspect` when you need the endpoint's parameters, response schema, examples, or access requirements. It is optional when the contract is already known.

## Call Effective

- `list`: browse a collection and choose the fields needed for the task.
- `read`: retrieve full item or collection data. Follow an item's `$uri` when available.
- `mutate`: create, update, or delete supported data within the user's requested action. Confirm the target and required inputs; discovery alone does not authorize a change.
- `whoami`: identify the connected account when relevant. It is not a prerequisite for other tools.
- `feedback`: tell Effective that the connector could not do what the user asked (see below).

Use `effective://` URIs supplied by the tools. To translate a documented API URL, replace its HTTPS origin and `/api/v2` prefix with `effective://api`, preserving the remaining path. Replace path placeholders with actual identifiers. Put query inputs in `parameters.query` and request bodies in `parameters.body`.

Do not invent identifiers, supported filters, or endpoint capabilities. Inspect or discover an appropriate lookup when an identifier is missing. Keep the user's requested constraints intact.

## Downloading files

- To read a file, read `effective://api/files/{fileId}/text` in pages, or an item's own `/text` link, such as a regulatory document's. For small files, `effective://api/files/{fileId}/contents` returns the original file in the tool result over the MCP connection, so it works in a network-restricted sandbox.
- `effective://api/files/{fileId}/download` returns a temporary signed link. A person can open it in their own browser. A sandboxed agent can fetch it only if the host in `networkRequirement.host` (usually `files.effectiveai.app`) is on the session's network allowlist.
- If fetching the link is refused, tell the user which host to allow and that they allow it in their network or sandbox settings. Do not drop the link quietly: for a file too large for `.../contents`, the link is the only way to get the original bytes.

## Common tasks

Translate the user's language into the documented capability, then select the endpoint. These are starting points, not mandatory sequences.

| What the user asks | How to approach it |
| --- | --- |
| “Compare competitors' rate changes for this line and state.” | Find relevant filings and read extracted rate impact and supporting actuarial documents. Distinguish filed, approved, and effective changes. |
| “Compare these endorsements, exclusions, or form editions.” | Find the form schedules and read the actual wording. Show differences with source references. |
| “Review the actuarial support for this change.” | Read the actuarial memo and available exhibits. Explain assumptions, units, and data gaps; do not treat a filing-level change as an individual quote. |
| “Benchmark this carrier'

Preview of the first 4,000 characters. Read full instructions →

Release notes

Updated the plugin description, capabilities and example prompts to show what Effective does for insurance teams.

Declared in the saved package. Remote tools may change independently.

Package details

Publisher declarations from the archived package. These are separate from our research and the live service's terms.

Package license
MIT
Package author
Effective AI, Inc.
Keywords
See keywords
Commerce declaration
Does not support commerceThis does not establish whether access is free or paid.
Review scenarios
5 positive · 3 negativeScenario counts, not test results.

Declared capabilities

  • See competitor rate and form changes with the filing behind them
  • Review the assumptions and sources behind a rate change
  • Compare coverage wording, exclusions and endorsements
  • Prepare working filings and answer objections

Package observed Nov 6, 2026.

Technical details
First seen
Oct 24, 2026 · 12:40 UTC
Last seen
Nov 6, 2026 · 06:00 UTC
Collection status
Collected

plugin_asdk_app_6ad15805c1e88191bb4c39db30b54966

Download plugin data (JSON)