How it works
Specification first
Every agent starts as a written specification: purpose and scope, workflow, the tools it calls, memory, guardrails and the points where a human must approve, handoffs to other agents, and an evaluation set graded across five levels (L1-L5). Quality is defined before anything is built.
Interest decides what gets built
Register interest on any agent or MCP server. The agents with the most demand are prototyped first, then piloted with design partners.
| Stage | What exists |
|---|---|
| Backlog | A researched description of the agent and where it fits in the workflow |
| Specified (concept) | Full specification, tool schemas and an evaluation set |
| Prototype | A working demo against synthetic data |
| Pilot | Deployed with a design partner |
| Production | Generally available under licence |
MCP servers
Agents reach your systems through MCP (Model Context Protocol) servers - loan origination, document intelligence, bureaus, claims, custodians and more. Where no server exists for a system, one can be built from that system's API.
Deployment
Licensed agents and their MCP servers are delivered as containers and deployed into your environment. Credit decisions, consumer contact and investment advice keep a human approval step.
What we don't publish
Prompts and evaluation cases are not published. Specifications show what each agent does, how it is controlled and how it is evaluated.