Claude Verisk Underwriting Intelligence connectorWhat Claude can do in your Verisk Underwriting Intelligence account.
The Claude Verisk Underwriting Intelligence connector exposes 4 tools. All 4 read ISO loss cost data, 0 write and 0 are undocumented. Below: what each one brings back, what your Verisk access must cover, and where Verisk and Anthropic disagree.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when Claude can query ISO loss costs
Instead of navigating specialised ISO tools and reports, you ask Claude a question about a line of business and a state, and it pulls the answer from Verisk's loss cost data itself. Verisk aims the connector at underwriters, actuaries, product managers and filing teams who work with filed changes, experience trends and review details.
Trace the history of filed changes. iso_losscost_activity_get returns recent filed ISO loss cost changes with summaries of their impact, the base for a comparison between two states.
Read the experience behind future indications. iso_losscost_experienceindex_get covers loss experience trends and pure premium movement, after you confirm the segments and the rolling period.
Understand a current review. iso_losscost_indications_get details indicated and selected changes by coverage, class and territory, with the trend selections behind them, while iso_visualizer_skill_include helps render the ISO data.
What it does not do is just as clear. Verisk calls the tools read-only: Claude cannot file a circular, edit an indication or push anything back to ISO. It only reaches the ISO products your Verisk account is entitled to. And it never runs on its own: no new filing triggers a message. Event-driven work belongs to automation platforms, listed in the Integrations hub, which do a different job rather than a better one.
Five words before you connect
The Claude vocabulary this page uses, in one minute.
- Connector
- A link you set up once between Claude and an account you already hold, so Claude can work with that account while it answers.
- Tool
- One named thing a connector lets Claude do. Claude chooses the tools it needs while answering, and the directory lists each by name.
- Authorization
- The sign-in screen of the service itself, where you hand Claude the access it will use. Granted once per person, and it can be revoked.
- Approval
- The confirmation Claude waits for before doing something that changes an account, shown in the conversation when the moment comes.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as Verisk's.
Connect Verisk Underwriting Intelligence in three steps
- 01
Find it in Claude
Open Claude's settings, go to Customize and then Connectors, and look for Verisk Underwriting Intelligence. On a Team or Enterprise workspace, an Owner or Primary Owner enables the connector before members can each sign in.
- 02
Sign in to Verisk
Click Connect on its row, then log in to Verisk in the window Verisk opens. Verisk requires multi-factor authentication, so keep your authenticator at hand. If the link breaks later, Disconnect and connect again.
- 03
Review the authorization
Read the authorization screen before you accept it. It belongs to Verisk, not to Claude, and it decides what the access covers. Verisk also has you set a permission level for each of the four tools once connected.
The 4 tools, all on the reading side
Verisk Underwriting Intelligence gives Claude 4 tools: 4 that read your account, 0 that change something in it.
Four tools that read ISO data. Their names stay exactly as Claude shows them.
- 4 read
What Claude reads (4)
4 toolsFour tools that fetch or render ISO loss cost information and change nothing.
iso_losscost_activity_get
Retrieves the recent history of filed ISO loss cost revisions, each with a summary of its impact, so Claude can line up what moved, where and by how much over the years.
iso_losscost_experienceindex_get
Covers loss experience trends, pure premium movement and the data that feeds future indications. Before answering, it asks you to confirm which segments you want and which rolling period: 1, 2, 3 or 5 years.
iso_losscost_indications_get
Brings back key details from ISO's loss cost reviews: indicated and selected adjustments by major coverage, class and territory segments, plus the trend selections and other components that drive the result.
iso_visualizer_skill_include
Works as a helper next to the three data tools: Verisk says you do not call it yourself, it is included automatically so Claude can render ISO information.
What Claude checks with you first
By default, Claude stops and asks before each action it takes on an account for someone. The prompt shows up in the conversation when it matters.
On Team and Enterprise workspaces, owners decide whether a member may let some actions pass without being asked every time, and they can cap what a connector may do across the organization, a choice nobody overrides from a personal account. Claude also works with the rights of the person who connected: Verisk says the connector inherits your existing entitlements, so a line or jurisdiction you cannot open on ISOnet stays closed in Claude too.
Which plans include it
None of the 819 sheets in the official directory shows plan availability. Connector by connector, that answer is published nowhere.
The published rule is general: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, and on Team and Enterprise an Owner or Primary Owner enables a connector for the organization first. Verisk's own page states something narrower about this connector; the limits section below sets both texts side by side. For the live state, check the connector's sheet in the official directory.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers, so nothing happens when ISO files a new circular or an index is refreshed.
A tool list that shows only reading is an observed floor, not a promise in Anthropic's terms: an administrator can open actions that appear on no public sheet. Here, Verisk itself states that the tools only retrieve data. The partner badge is not a security audit, and Anthropic says on every sheet that it neither chooses the tools a publisher exposes nor guarantees their behaviour. All connector details on this page come from Verisk; no Claude help article covers it. Automation platforms, for event-driven flows, sit in the Integrations hub.
Which Claude plans can use this connector?
- Claude help center, general connector rule ↗September 2026Remote connectors are open to all users; on Team and Enterprise an Owner has to enable each one first.
- Verisk's connector page ↗April 2026The publisher states that this connector is for use only with Claude Enterprise plans.
What this page followsNeither text is outdated: Anthropic's rule covers every connector, while Verisk's sentence targets this one alone and is therefore more specific. It is the publisher speaking, not Anthropic, so check the directory sheet on your own account before relying on either.
Need help connecting Verisk Underwriting Intelligence to Claude?
A person reads every message.
