Someone just had a crash and does not know what their policy covers.
Cautelia.
Takes the report, checks the policy, hands it to an AI adjuster. A portfolio project on how real agents are built.
Someone just had a crash and does not know what their policy covers.
Cautelia takes the report by voice or text, finds the answer in the insurer’s policy and leaves the decision to an AI adjuster that explains it. A portfolio project.
Why this exists
Not another wrapper.
Calling a model is the easy part. Cautelia shows what most demos skip: what happens when the provider fails, where the state lives, where each figure comes from, and proof that it works.
- Every citation verified
- Insurers kept apart, tested
- Data redacted in logs and traces
- An AI adjuster decides coverage
- Takes the report4 turns
- Reads the policy2 clauses
- Checks the citationverified
- Reviews the case3 checks
- An AI adjuster decideswith the trace
How it works
One orchestrator. Specialist agents. Small shared state.
Code, not the model, decides which node handles each turn. Nodes return structured results, never raw reasoning, so the context stays small and the trace reads top to bottom.
- Voice layer
- Orchestrator
- Specialist agents
- Tools
- AI adjuster
- 01
Orchestrator
Routes each turn in code and decides when the AI adjuster steps in.
- 02
Intake
Gathers who, what, when and where while the caller talks, in any order.
- 03
Policy verification
Cites only clauses that exist, belong to that policy and are in force. “Nothing found” and “could not check” are different answers.
- 04
Decision
Applies the insurer’s versioned, tested rules. The model never picks the category.
- 05
Compliance
Reviews the case before it closes.
Voice
Fast enough to feel like a call. Patient enough not to interrupt.
- Streaming speech to textstreams
- End-of-turn detectionwaits for meaning
- Orchestratorroutes
- Tool callsvalidated
- Streaming text to speechstreams
- The hard part is knowing when someone has finished. Cautelia waits for meaning, not silence: whoever dictates a plate pauses mid-number.
- The caller can interrupt. The agent stops mid-sentence, keeps the state, and picks up where the caller left it.
- The heavy work (policy checks, rules, compliance) never runs inside the turn, so answer time does not depend on how many rules an insurer has.
Scripted example, not a recording
- Caller
Hi, I had a fender bender this morning, nobody's hurt.
- Agent
Glad everyone's okay. I'll open the claim while we talk. Where did it happen?
- Caller
On the highway, near exit 12, around eight.
- Agent
Got it: highway, exit 12, about 8 a.m. Was the other driver's information exchanged?
Guardrails
The agents gather. An AI adjuster decides.
A report is intake and coordination, not judgment. Cautelia never says something is covered, never denies it and never mentions amounts: it hands the case to an AI adjuster that decides and explains each step with its sources.
- Before the model: outside text enters as data, never inside the prompt.
- In flight: every tool call is validated against its schema.
- Before anything leaves: every message, errors included, passes one exit guard.
- Above all: if someone reports a serious injury, the agent stops collecting data and gives the emergency phrase.
Evals
Every change is tested. What fails is shown.
Scripted conversations with known answers run on every change. Pass or fail per case, Spanish and English apart, never averaged. A failing case stays visible: it is never removed to make a number go up.
Every call leaves a nested trace, so a claim can be followed from the first word to the closed record.
What gets measured
- ✓Latency per turn, end to end01
- ✓Interruptions handled without losing state02
- ✓Completeness of the FNOL record03
- ✓Latency per turn, and stop time on interruption04
- ✓Zero personal data in logs or traces05
See it run.
Describe a made-up crash, by chat or by voice, and see what it does. Nothing to install.