Collision Intelligence does not live in a browser tab. There is no chatbot for the estimator to prompt. The agents are trigger-based reflexes — asynchronous routines that fire on specific events inside the systems your shop already uses, then push their output directly back into CCC, Mitchell, Audatex, the rental portal, or the technician's phone. The shop hosts nothing. Anthropic runs the compute.
Every agent in this catalog is built on the same skeleton. A signal arrives from the outside world. A Claude Code routine reasons about it against shop policy, OEM procedures, and DEG rulings. A structured output is written back into a system the shop already operates. The estimator is never asked to open a new tab.
The signal. An event happens in a system the shop already uses — a CCC Secure Share webhook fires, a sublet PDF arrives in the estimating inbox, a VIN is decoded as a BEV, an ECD field changes in the SMS.
The thinking. A Claude Code routine runs on Anthropic's infrastructure. It reasons over the trigger payload, retrieves the shop's policies, pulls the OEM procedure, checks DEG, consults part catalogs — then decides what to write.
The artifact. A structured write lands where the humans already look. Not a Slack "FYI" — an actual line item, an actual rental extension, an actual compliance checklist on the tech's phone, an actual session URL for the one case a human must review.
The AI model is the commodity. The trigger is the product. Anyone can call Claude; almost nobody in collision has wired the trigger to the insurer's webhook, the DEG ruling, and the adjuster's inbox at the same time.
Routines are Anthropic's managed runtime for asynchronous agents. They launched in 2026 and are the substrate the Collision Intelligence catalog is built on. A routine is defined once — a prompt template, a trigger, and a set of MCP connectors — and then runs 24/7 on Anthropic infrastructure. There is nothing to install in the shop.
0 */1 * * * hourly for ECD drift scans. 0 6 * * 1-5 at 6am weekdays for morning triage.text field carrying the payload context. CCC Secure Share and Mitchell both fire here.Every routine invocation carries a bearer token in the Authorization header. The shop never issues or stores this — Intersection Strategies rotates tokens centrally. The body is a JSON object; the one required field is text, which contains the natural-language context the routine reasons over.
The routine returns a structured JSON body. One field is load-bearing: claude_code_session_url. When the routine hits a case it cannot resolve with high confidence — an adjuster pushback that invokes a novel carrier policy, an OEM procedure not yet in the vector store, a VIN outside the supported car parc — it writes a URL where a human can step into the session mid-flight and finish the reasoning. This is the human-in-the-loop safety valve. No autonomous action is ever taken on ambiguous cases.
Runs 24 hours a day on Anthropic infrastructure. The shop hosts nothing, maintains nothing, updates nothing. Agents get smarter when the underlying Claude model gets smarter, automatically. This is the single most important architectural fact for a shop operator to internalize.
Every agent is described internally using a three-column frame: what it senses, what context it enriches the signal with, and what action it takes. This frame maps cleanly to the three-tier commercial structure — Observation Fee, Intelligence Premium, Resolution Bounty — so a shop can see exactly what they are paying for at each stage.
The agent watches a system you already operate and notices an event the moment it happens. A new assignment. An ECD field change. A sublet PDF in the inbox. A VIN decoded as BEV. Observation is continuous, silent, and requires no human action to invoke.
Example: Agent 4 observes an FNOL payload land in the CCC Secure Share webhook and reads the VIN, claim number, and damage descriptor.
The raw signal is useless without context. The agent retrieves the shop's policies, the OEM procedure, the DEG ruling, the state's E01 threshold, the carrier's specific DRP profile, the current parts pricing — everything a veteran estimator would pull from memory before writing a line.
Example: Agent 4 pulls ACV from a valuation API, loads the state's E01 percentage, and fetches historical teardown compensation data for the insurer.
An observation with context is still not revenue. The agent must write back — into the estimate, into the rental portal, into the tech's phone, into the carrier's communication channel. This is where gross profit is defended or lost. Actions are audited, reversible, and always leave a paper trail.
Example: Agent 4 pre-appends Teardown, Admin Total Loss, and Hazard Storage lines to the estimate — before the technician touches the vehicle.
The agents talk to the systems your shop already runs. Every integration below is documented by its vendor, uses a real API endpoint, and has a named standard behind it. No proprietary protocols. No "contact us for access."
| System | Role | Protocol / Standard | Endpoint / Reference |
|---|---|---|---|
| CCC Secure Share | Primary estimating & claim exchange — 28,000+ shop footprint | CIECA BMS JSON / XML, webhook push | cccsecureshare.com/Developers |
| Mitchell Transactional API | RepairCenter workfile read/write | OData REST | developer.mitchell.com/apis |
| Audatex / Solera Qapter | Secondary estimating for Solera-dominant MSOs | OAS3 Swagger, REST | us-services.auda-target.com/ APIGateway/swagger |
| Enterprise ARMS | Rental authorization & ECD extension | Web portal automation, form fields | armsweb.ehi.com |
| Hertz HIRS | Alternative rental portal (carrier-routed) | Web portal automation | fleetsupport.maintenance. hertz.io |
| OEM repair portals | Authoritative procedure documents | Toyota TIS, OEM1Stop, I-CAR RTS scrapers | techinfo.toyota.com · oem1stop.com · rts.i-car.com |
| DEG (Database Enhancement Gateway) | Industry-maintained inquiry layer — canonical "not-included" citations | HTTPS + structured inquiry ID lookup | degweb.org |
| VIN decode API | Powertrain classification (ICE/PHEV/BEV) on intake | NHTSA vPIC REST, private vendor fallback | vpic.nhtsa.dot.gov/api |
Every routine is authored in the same MISSION / INPUT DATA / SURGICAL STEPS / CONSTRAINTS template. The template forces the agent to behave like a disciplined technician, not a generalist chatbot. Below is the actual prompt used for Agent 4 — the E01 Pre-Cognition & Teardown Defender.
This prompt is versioned in git. Every change is reviewed. Every shop gets their own variant — labor rates, state thresholds, DRP overrides, and the shop's own teardown hours matrix are injected at routine compile time.
A collision shop handling claims data is a Third-Party Service Provider handling Nonpublic Information under NY DFS Part 500 — whether it knows it or not. Every architectural decision in Collision Intelligence is downstream of that classification. The shop owns the data. Anthropic runs the compute. Intersection Strategies owns the routines. No party sees more than the minimum it needs.
Every routine invocation carries a rotated bearer token. Tokens are scoped to a single shop and a single routine. Revocation is instant. No shared secrets. No passwords in code.
The shop is classified as a TPSP handling NPI (claim numbers, VINs, insured names). Collision Intelligence is architected so the shop never exports NPI to an unmanaged destination. Vendor risk diligence is documentable.
Every routine that encounters ambiguity returns a claude_code_session_url. A human estimator steps into the live session and completes the reasoning. No silent autonomous action on ambiguous cases.
Every action — every line written, every rental extended, every alert posted — is logged with a timestamp, a trigger ID, the specific P-Page or DEG citation used, and the routine version. Immutable. Exportable for a NAIC audit.
Per-routine, per-shop rate limits prevent a runaway cron from spamming the CCC workfile or the rental portal. Circuit breakers trip on anomalous output volume and hand the operation back to a human before damage is done.
Every new routine starts in shadow mode — it reads, scores, drafts, but does not write. Write access to CCC, Mitchell, Audatex, and the rental portals is granted only after the shop operator approves the routine's draft output for a defined period.
The shop owns every byte of claim data that passes through the system. Anthropic's enterprise terms prohibit training on customer payloads. Intersection Strategies retains only the minimum metadata required to operate and audit the routines — trigger IDs, timestamps, confidence scores, actions taken. On contract termination, all shop-specific routine variants and stored context are purged within 30 days.
Anthropic's Routines runtime — the asynchronous, trigger-based agent substrate this catalog is built on — shipped to general availability in early 2026. Before Routines, every agent had to be a chatbot. There was no native way to express "fire on a webhook, run 24/7, hand off to a human on low confidence." That is now a first-class primitive.
The enterprise AI landscape has materially shifted. Fortune 500 workloads that ran on GPT-class models in 2024-2025 are migrating to Claude on the basis of tool-use reliability, longer context windows, and Anthropic's enterprise data posture. Collision Intelligence is built where the traffic is going, not where it was.
Collision repair has not been won. CCC, Mitchell, and Solera ship estimating platforms; nobody ships trigger-based reflexes that sit on top of them. The first vendor to put a disciplined, audited, trigger-based agent in a shop operator's workflow — with real integrations and real audit logs — owns the category.
The shop that adopts Collision Intelligence in 2026 is not paying for a model. They are paying for every trigger that has been wired, every DEG citation that has been indexed, every carrier quirk that has been catalogued. The model underneath gets better for free. The moat is the wiring.