Internal APIs

Internal APIs, agent-ready

Register APIs from Postman collections, OpenAPI / AsyncAPI, or your Private API Network. Agents reach them on the same control plane as LLMs and MCP.

Register your APIs once, reach them from every agentPostman collectionsOpenAPIAsyncAPIPrivate API NetworkFabric GatewaySame policy layerAuth · RBAC · CredentialsAgentsSame control plane as LLMs and MCP
A data plane in your VPC reaches private APIs that a SaaS gateway cannot, under the same policies as every other route.
4
ways to register an API
1
control plane for LLMs, MCP, and APIs
In VPC
reach private APIs inside your perimeter

The problem

Agents need your internal APIs, but exposing them directly means new credentials, new auth paths, and a separate governance story from the rest of your AI traffic.

How it works

Register an API from a Postman collection, an OpenAPI or AsyncAPI spec, or your Private API Network. Fabric then serves it to agents on the same control plane as models and MCP servers, with the same policies applied.

What you get

Same policy layer

Auth, RBAC, and credential brokering, identical to LLMs and MCP.

Inside your perimeter

A data plane in your VPC reaches private APIs a SaaS gateway cannot.

Bring every AI interaction under control

Connect your first model, MCP server or internal API and apply consistent governance from one gateway.

Sign upRead the docs