Your advisers answer from the carrier document, not from memory.
One methodology question, scoped to a market and a product line, answered from published insurer documents. Every answer arrives with its sources and a trust state, so compliance can check it.
Where it runs today: your team reads it in the Emable workspace, signed in and your own systems call it over the REST API.
What changes
Who inside your organisation is better off, and what they can show for it.
Head of Advice at an adviser network
Advisers get a cover answer with the document behind it, instead of a colleague's recollection or a call to the carrier.
The output schema requires answer, sources and trust_state on every response. Source: the emable capability catalogue, insurance-assistant.
Compliance Lead at an insurer or distributor
They can check what was said against the actual wording, because every answer names the document it came from.
Sources are returned with each answer. The manifest states plainly that this does not replace regulated professional advice.
Product Lead at an insurer
An answer surface goes into the client app or the adviser desktop without first building a document pipeline.
Declared surfaces are the specialist workspace and REST. The corpus catalogue is machine readable at GET /v1/insurance/catalog.
AI Product Lead at a bank or fintech building an assistant
Their assistant gets a grounding call, plus a signal that says when an answer is thin before a client sees it.
The tool returns trust_state alongside the answer so a caller can tell a well grounded answer from a thin one. Source: manifest agent description.
Head of Product at a distributor working several markets
They can see which markets and product lines are actually covered before promising an answer surface to a partner.
The catalogue is public and unauthenticated, and it separates documents published by the provider from documents supplied under a distribution relationship.
Two ways to get it
Have it delivered, or let your own AI call it.
As a service
We deliver the assistant on the markets and product lines you actually distribute. First we check corpus coverage for those markets and say plainly where it is thin. Then we wire the answer surface into your adviser desktop, your client app or your own assistant, over POST /v1/insurance/ask. We agree with your compliance what a grounded answer has to show before an adviser ever sees one. Write to us with your markets, your product lines and the surface you want it in. There is no self-serve run on this page. A person replies and we agree the scope first.
Tell us what you needOne message, no form. We answer with what it would take.
Through your own AI
Add the Emable connector once and your own assistant calls ask_insurance on https://api.emable.ai/mcp-emable. It asks one methodology question, scoped to a market and optionally to a product line and a language. The answer comes back with its sources and a trust state, so your assistant can tell a grounded answer from a thin one. The tool appears only when your credential carries the insurance:ask scope. Your own backend can call the same capability over POST /v1/insurance/ask. It works in Claude, ChatGPT, Codex and any MCP client.
- Connector
- https://api.emable.ai/mcp
- Tools it adds
ask_insurance
What your AI can answer
Connect it once, and your assistant answers these.
Questions in your own words, each one landing on a published tool. Ask us and we answer the same ones for you.
- 1Does travel cover pay out when the airline cancels the flight, and when does it not?
ask_insurance - 2What do the binding terms say about this exclusion, rather than the summary?
ask_insurance - 3What is in the IPID for this product, and what does the full wording add?
ask_insurance - 4What does the assistance annex exclude for winter sports in Czechia?
ask_insurance - 5What are the underwriting acceptance rules for this product line?
ask_insurance - 6Which carrier document is this answer taken from, and which class of document is it?
ask_insurance - 7How well grounded is this answer before I let an adviser repeat it to a client?
ask_insurance - 8Can I have the same answer in the adviser's working language?
ask_insurance
Insurance Assistant answers these through the tools above. A question outside them is refused, not guessed.
What it rests on
The evidence, and the edges.
Evidence
- Status live, exposure public, markets EU, data class derived. Source: the emable capability catalogue, insurance-assistant.
- Every response carries an answer, a source list and a trust state. The output schema requires all three.
- Sources are published insurer documents indexed in the Emable European insurance corpus. Source: the emable capability catalogue.
- Document classes the corpus holds: policy wording, the IPID under EU 2017/1469, and the carrier product sheet.
- The corpus catalogue is public and machine readable at GET /v1/insurance/catalog. The coverage page at /assistant/coverage reads it live.
- The catalogue separates documents published by the provider from documents supplied under a distribution relationship.
- Corpus catalogue and source metadata are read at request time. Source: the emable capability catalogue.
- Callable today as ask_insurance on https://api.emable.ai/mcp-emable. Source: the emable capability catalogue.md.
- Charging unit: one limited corpus question. Credits are the platform's metering unit, not a price.
- Not enough verified runs yet. Public statistics appear only after 20 verified runs across 5 different accounts.
Corpus catalogue and source metadata are read at request time.
What it does not do
- Answers only markets and product lines with verified corpus coverage.
- Does not replace regulated professional advice.
- One question per call, scoped to one market. No cross-market comparison in a single call.
- The input is a question, a market code, an optional product line and an optional language. There is no upload field.
- In a trial run: published corpus only, no document upload, three runs.
- No self-serve run on this page. Every route starts with a person or a connected client.
- This page names no insurer. Which providers are covered sits in the published catalogue.
Verified usage
Not enough verified runs yet
Public statistics appear only after 20 verified runs across 5 different accounts.
The contract, for the people who will wire it
Status, permissions, tools, schemas and where it runs. The same values the API returns, so nothing here can drift from what your client will actually get.
Status, access and price
- Status
- Livepublic
- Provider
- emable
- Manifest version
- v1.0.0
- Countries
- EU
- Data class
- derived
- Access
- read
- Permissions
account:readinsurance:ask
- Charging unit
- One limited corpus questionPricing model: per query.Credits are the platform's metering unit, not a price. We quote the engagement.
Tools and schemas
Ask insurance methodology
ask_insurance
Ask one insurance-methodology question against Emable's published European corpus so you can answer with citations instead of a guess.
Use it when
- The user asks a specific coverage, exclusion, underwriting, or pricing question for a market the corpus covers.
- The answer needs to cite the actual carrier document, not a paraphrase.
- You want an explicit trust signal before repeating the claim downstream.
Do not use it when
- The market or product line has no verified corpus coverage — check https://api.emable.ai/v1/insurance/catalog first.
- The user needs binding legal or regulatory advice, not methodology guidance.
Returns
A qualified answer, trust state and source list.
Arguments
| Name | Type | Required | Description |
|---|---|---|---|
| question | string | yes | The insurance-methodology question. |
| country | string | yes | ISO-2 market code, e.g. CZ, ES. |
| product_line | string | no | Product line to scope the answer to. |
| language | string | no | Preferred answer language. |
Example: Ask about a Czech travel-assistance exclusion
{
"question": "What does the assistance annex exclude for winter sports?",
"country": "CZ",
"product_line": "travel"
}{"answer": "...", "trust_state": "grounded", "sources": [{"document_class": "assistance", "carrier": "..."}]}
Errors a caller must handle
invalid_api_keyThe credential is absent, invalid, expired, or revoked.Stop and reconnect with a valid key or OAuth grant.missing_scopeThe identity lacks the `insurance:ask` scope this tool requires.Request `insurance:ask` and reconnect.422Input does not match this tool's schema.Correct the input using the schema returned with this tool.capability_runs_disabledExecution is temporarily off for this capability.Keep discovery available and retry later; this is not a permanent failure.
Input schema
{
"type": "object",
"properties": {
"question": {
"type": "string",
"minLength": 3,
"maxLength": 1500,
"description": "The insurance-methodology question."
},
"country": {
"type": "string",
"minLength": 2,
"maxLength": 2,
"pattern": "^[A-Za-z]{2}$",
"description": "ISO-2 market code, e.g. CZ, ES."
},
"product_line": {
"type": "string",
"maxLength": 80,
"description": "Product line to scope the answer to."
},
"language": {
"type": "string",
"maxLength": 20,
"description": "Preferred answer language."
}
},
"required": [
"question",
"country"
],
"additionalProperties": false
}Output schema
{
"type": "object",
"properties": {
"answer": {
"type": "string"
},
"sources": {
"type": "array",
"items": {
"type": "object"
}
},
"trust_state": {
"type": "string"
},
"confidence": {
"type": "number"
}
},
"required": [
"answer",
"sources",
"trust_state"
],
"additionalProperties": false
}Surfaces and connectors
No standalone MCP URL is deployed for this capability yet.
Specialist workspace, sign in requiredSources, limits and support
Sources
Published insurer documents indexed in the Emable European insurance corpus.
Limitations
Answers only markets and product lines with verified corpus coverage.
Does not replace regulated professional advice.