Every agent has its own private Hippo Fabric. Cortex connects them through the Connector Hub — a intelligent router that passes context, enforces policy, and lets the swarm coordinate without sharing a brain.
Enterprise Integration Hub
Every enterprise system your agents need is already connected through the Integration Hub inside Cortex. Agents describe what they need — the Hub resolves protocol, authentication, data transformation, and retry logic automatically. No connector configuration. No custom code.
Integration Hub
01 — Natural language
Agents describe what they need. The Hub translates intent into the right API call, with the right auth and schema — automatically.
02 — Protocol-agnostic
Whether the system is a modern SaaS API or a 20-year-old ERP, agents interact through a single unified layer.
03 — Enterprise-safe
All Integration Hub calls pass through Cortex's SafetyGate and are written to the ClickHouse audit log. Full traceability, zero exceptions.
Meet the Integration Architect
When an agent needs to connect to a new enterprise system, the Integration Architect takes over. It captures requirements in plain language, produces a formal integration spec, validates everything in a sandbox, then promotes to production — with a full Cortex audit trail.
Agent or human describes what they need in plain English. No jargon, no schema — just the outcome.
Integration Architect produces a formal machine-readable spec: systems, triggers, data mappings, auth, error handling, retry logic.
The spec runs in an isolated sandbox against mock data. Auth flows, response shapes, and edge cases verified before any production system is touched.
Validated spec promoted to the Integration Hub. Live, audited, and immediately available to every authorised agent in the swarm.
A developer writes a custom connector script, hardcodes credentials, ships it — and two months later nobody knows who owns it or whether it still works.
Requirements captured in natural language. Formal spec produced. Sandbox tested. Deployed with a full audit trail. Every connection is owned, versioned, and observable.
Why Cortex
LangGraph and friends orchestrate the calls. Cortex orchestrates the cognition. One builds a workflow. The other builds an organism.
Fixed workflows. Each node is a prompt. Context passed as messages. No shared memory. No learning between runs. Every conversation starts from zero.
Each agent owns its own Hippo Fabric. The Connector Hub routes context intelligently between them — enforcing policy, passing only what each agent needs. The swarm coordinates without losing cognitive independence.
How it works
01 — Specialisation
Intake, triage, researcher, executor, critic. Each agent has its own prompt, tools and personality — but they share the same memory substrate.
02 — Connector Hub
Each agent owns its own Hippo Fabric. The Connector Hub in Cortex routes context between them — passing only what is needed, enforcing policy at every hop. Isolation by default, coordination by design.
03 — Hebbian routing
When a handoff pattern resolves a case well, that path strengthens. Over weeks the swarm routes work optimally — without a single flowchart.
Coordinate
Deploy Cortex on top of Hippo Fabric. Start with two agents. Scale to hundreds.