Learn About Agent Fabric
AI agents, MCP servers, and APIs are built across multiple platforms. That makes reuse, consistent security, and end-to-end LLM spend tracking difficult. Agent Fabric is the control plane for that landscape.
-
Find every agent, MCP server, and API in the registry so you reuse what exists instead of rebuilding it.
-
Make the APIs, applications, and agents you already run available as tools, so agents can take action without a rebuild.
-
Put the same authentication, access, and security rules on live traffic, regardless of which platform built the agent.
-
See where token spend goes, cap it, and stop paying a frontier model for work a smaller model can do.
The end-to-end journey for Agent Fabric consists of these tasks, each with links to relevant content to assist you in completing them.
Learn About Agent Fabric Start with how the registry, agent actions, governance, and cost control fit together. Then pick a job. |
Discover Agentic Assets Catalog agents, MCP servers, and APIs so you reuse what exists. Keep that inventory current with scanners. |
Enable Agent Actions Make the APIs, applications, and agents you already run available as tools. Start by exposing existing APIs as MCP servers, and use an A2A bridge for agents that aren’t A2A-compliant. Add a broker only when work spans specialized agents. |
|
Apply Security and Governance Put Omni Gateway in the request path so authentication, monitoring, and policy run on live traffic. Define rules once, then apply them across agents, APIs, and MCP servers. |
Control LLM Spend Give agents one governed endpoint for multiple LLM providers. Then cap token spend and reduce what each call consumes. |
Observe Agent Traffic See how agents, brokers, and MCP servers connect. Watch latency, errors, and volume in production. |