Cogentic Link
Unified access channel supporting Cogentic CLI, HTTP API, and MCP calls.
Single entrypoint for Agent access — Core orchestration and policy execution · High-speed intelligent routing layer
Platform components
Four core components that together form the complete enterprise private tool governance architecture.
Cogentic Link
The single entrypoint for Agents
Unified access channel supporting Cogentic CLI, HTTP API, and MCP calls.
- CLI / HTTP / MCP calls
- Data channel across all layers
- Enterprise-grade security
Cogentic PolyCenter
Core orchestration and policy
Master controller integrating routing, linking, protocol adaptation, and state management.
- Policy execution & access management
- Protocol adaptation
- State & session management
Cogentic Router
High-speed intelligent routing
Low-latency bidirectional channel distributing requests to the right services and tools.
- Low-latency bidirectional comms
- Intelligent request dispatch
- Link tracing
Cogentic Hub
Unified tool provider management
Connect, publish, and manage CLI, OpenAPI Server, and MCP Server tools in one place.
- CLI / OpenAPI / MCP Server integration
- Tool library & category management
- Ecosystem integration & distribution
Agent → Cogentic Link → PolyCenter → Router → Hub → Tool Providers → Tool → Results via Link
How it works
From agent invocation to private tool execution in one flow.
Agent calls Cogentic Link
Your CLI agent or MCP client sends a tool invocation request through Cogentic Link — the single secure entrypoint.
PolyCenter orchestrates routing
Cogentic PolyCenter validates the request, applies policy, and delegates to the Router for intelligent dispatch.
Hub resolves the tool
Cogentic Hub looks up the tool library, identifies the target provider (CLI, OpenAPI, or MCP Server), and forwards the call.
Result returns via Link
The tool executes privately and results are returned through Cogentic Link to your agent — no ports exposed.
Data flow panorama
Every request travels through the same governed path — in, through the platform, to your tools, and back.
Request flow: Agent -> Cogentic Link -> Cogentic Platform -> Cogentic Hub -> Tool providers -> Tool execution -> Return through Link.
How to use
- 1
Install Cogentic Hub from GitHub and complete basic configuration.
- 2
Connect tool sources via CLI, OpenAPI Server, or MCP Server.
- 3
Build tool libraries and categories for governance and reuse.
connect tool library, save key pair \
<tool_library_name=your_key>
connect tool library <tool_library_name> \
to do something- 1
Install the `connect-tool-library` skill in your agent environment.
- 2
Save the tool library key with your agent.
- 3
Invoke tools in natural language through the skill.
Need help with rollout or enterprise deployment? Talk to us
Ship Link with confidence
You have the architecture — now wire Hub, skills, and policies into production. We help teams roll out governed tool access without slowing builders down.