Back to website
2-min read

AgentStatus × Sixfold

Independent, distributed assurance for production AI agents, alongside Sixfold's underwriting AI platform.

AgentStatus is how teams prove behaviour in the wild. Independent, distributed production assurance for AI agents with continuous checks, gold-based expectations, and alerting, run from 800+ nodes across 30 countries. We sit alongside Sixfold's Institutional Intelligence and the AI agents Sixfold deploys into carrier workbenches. We do not replace them.

20M+
validations
6,000+
agents
800+
residential devices
30+
countries
agentstatusagentstatus.dev | partner brief

What we understand about Sixfold

The first AI purpose-built for insurance underwriters.

Sixfold's platform brings AI agents directly into the underwriter's workflow, agents that triage cases, surface cited risk insights, score every submission 1 to 5 against carrier guidelines, write referral emails, and audit cases for compliance issues before binding. The latest advancement, Institutional Intelligence, encodes a carrier's risk appetite, underwriting guidelines, and historical decisions so the platform answers the way the carrier expects.

Sixfold operates with insurance-grade data governance and isolation, integrates via API into existing workbenches, CRMs, and policy admin systems, and is deployed in production at carriers including Zurich North America, Generali Global Corporate & Commercial, Skyward Specialty, and Mosaic. Backed by a Series B from Brewer Lane Ventures, with strategic investment from Guidewire Software, Bessemer, and Salesforce Ventures.

What AgentStatus is

Continuous, controlled validate traffic against production agent surfaces.

AgentStatus runs continuous, controlled validate traffic against production and staging agent surfaces, with gold libraries, drift detection, and alerting for teams that need clear, repeatable evidence when things break or drift.

That includes multi-turn flows and multi-agent journeys when real underwriter paths span tools, escalations, and case handoffs. It maps cleanly to governance and risk conversations when carriers, regulators, or auditors ask what ran, from where, and what changed.

For agents shaping submission triage, risk scoring, and referral decisions, the cost of an undetected behaviour shift is not a UX issue. It is loss-ratio exposure.

Where we fit

Complement, not overlap.

01

Eval-time accuracy vs production drift

Sixfold's models are evaluated against carrier guidelines at training and deployment time, the foundation. AgentStatus answers a different question: a quarter into deployment, after model updates and changes to a carrier's appetite, is the agent still scoring submissions the way Institutional Intelligence said it should?
02

Inside-out scoring vs outside-in evidence

A 1 to 5 appetite-fit score reported inside the workbench is a strong inside-out signal at the moment of decision. Distributed validate traffic catches the cases where the same submission, on a different network, against a refreshed model, starts producing a different score, before a quote goes out misaligned with the carrier's risk appetite.
03

Global execution footprint

800+ nodes across 30 countries is the proof we are not synthetic from a single cloud region. For Sixfold's carrier customers operating across multiple geographies, lines, and partner integrations, it matters that the assurance layer validations from where the actual submissions originate, including Lloyd's Market specialty lines, where Sixfold is now present via Cohort 12.
04

Partner-friendly integration posture

We do not assume we can discover Sixfold customers the way some web-widget vendors can be scraped. Credential-based surfaces (sandbox API access, customer-approved monitoring, joint customer scenarios) are the right model, aligned with the SOC 2 / data-isolation posture Sixfold already maintains for its carrier customers.

The split

Two truths, one story.

Sixfold, inside-out

  • Institutional Intelligence
  • 1-5 appetite-fit scoring
  • Cited risk insights
  • Referral & compliance agents
  • Workbench / CRM / PA integration

AgentStatus, outside-in

  • Continuous validate traffic
  • Gold libraries & drift detection
  • Multi-turn / multi-agent journeys
  • Real-network execution evidence
  • 800+ nodes across 30 countries

Proof of scale

Plain definitions, no inflation.

In about two months, we have executed on the order of 18 million validate runs across the network. We also maintain on the order of 6,000 agent records in our system, meaning rows and configurations we track, including evaluation and pipeline agents, not "6,000 paying customers."

We have also caught node operators trying to game the network with datacenter VMs instead of real consumer egress. Detection of adversarial behaviour is built into the product. If helpful, we can share stricter production-only definitions under NDA.

What we are not claiming

An independent layer that coexists.

We are not a replacement for Sixfold's Institutional Intelligence, agent library, or workbench integrations. We are an independent layer that can coexist with them, and where useful, help carriers correlate outside-in validate outcomes with inside-out scoring accuracy, so underwriting leaders have continuous evidence that the deployed agent is still behaving the way the carrier's appetite requires.

What we'd like from this conversation

Asks.

01

Validate the fit

Where do Sixfold's carrier customers want independent assurance for agent output, and where does Sixfold prefer everything native to the platform?

02

A practical next step

A sandbox agent we can validate with gold prompts representative of an underwriting workflow (submission triage, appetite-fit scoring, referral generation), so Institutional Intelligence and AgentStatus drift detection tell one story together.

03

Partner path

If there is a partner path, we'd like to understand supported integration patterns for carriers operating across multiple geographies and lines, particularly through Sixfold's strategic alliances with Guidewire and across the Lloyd's Market.

Closing

Sixfold helps carriers build and operate AI agents that bring joy back to underwriting. AgentStatus helps those same carriers prove, continuously, that those agents behave

the way appetite, regulators, and brokers require, globally, with evidence that holds up under scrutiny.

Metrics are stated with explicit definitions: validate runs are scheduled executions over ~two months; agent records are database rows, not revenue customers. Public Sixfold references above reflect Sixfold's public product pages, customer disclosures, and Series B announcement as of the date of this note.