Learn
CortexHub puts AI to work safely: organization-owned agents, a personal co-worker for every member, a governed gateway for outside AI tools, and one layer of governance over every action. These pages explain the product model in plain language for members, admins, and developers.
One gateway, many integrations
Your assistant talks to CortexHub once. CortexHub connects to the tools your workspace allows.
Your AI app
Claude, Cursor, Windsurf, VS Code, or your Python agent runtime connects over MCP.
MCP + OAuth
CortexHub gateway
One endpoint. Search, policy checks, approvals, and audit on every call.
Governed invoke
External tools
Slack, Notion, GitHub, Jira, HubSpot, Stripe, and other integrations your workspace enabled.
Start here
| Topic | For | Summary |
|---|---|---|
| What is CortexHub? | Everyone | The problem we solve and the core surfaces |
| How it works | Everyone | Connect, discover, invoke under governance, audit |
| Organizations | Admins, partners | Account model and roles |
| Agents | Everyone | Org Agents, co-workers, and external gateway identities |
| Toolkits and connections | Everyone | Catalogue, entitlement, connect once |
| Groups and access | Admins | Layered rules that only get stricter |
| The Brain | Members | The living map your co-worker builds, and how to correct it |
| Meetings | Members | Your co-worker as an active meeting participant |
| Sessions and activity | Everyone | What appears in Cloud |
| Usage | Everyone | One view for activity, spend, and savings |
| Authentication | Developers | OAuth on the gateway and Platform API |
| Glossary | Everyone | Canonical terms |
Choose your path
- Connect from an AI app → Get started
- Set up an organization → Admin guide
- Build with the SDK → MCP SDK
- Automate with REST → Platform API Reference