Cost Controls
Track tokens and cost across every team, user and agent, set budgets and token-aware limits, and stop runaway spend in real time.
AI spend grows one team and one agent at a time. Provider invoices arrive as a single number, so nobody can say which team, user or agent drove it, and the first sign of a runaway agent loop is the bill. Limits set in each application drift, and they never cover the agents nobody registered.
Every model call goes through the Fabric data plane with a verified identity attached, so Fabric can count tokens and cost on the way through and attribute them to the team, user and agent behind the request. Analytics breaks spend down along those lines and by route, model and namespace. Token-aware limits stop a request before it reaches the provider once a budget is used up, and the killswitch cuts off a scope immediately. To lower the cost of each request as well, pair it with Adaptive Model Routing, Lightyear and MCP Tool Search.
Tokens and cost attributed to whoever made each request.
Cap requests and tokens per team, route or consumer, enforced in the gateway.
Break spend down by route, model and namespace, down to a single trace.
Block traffic for a tenant, service, route or tool immediately.
Each team sees and manages its own spend.
Every request reaches the Fabric data plane with a verified identity attached. Fabric counts the tokens and cost of each call on the way through and records them against the team, user and agent behind it, so analytics can break spend down along those lines.
Token-aware limits are enforced in the gateway: once a limit is used up, the request is rejected before it reaches the model provider, so it is never billed.
Yes. The killswitch blocks traffic for a tenant, service, route or MCP tool scope at once, without a deploy.
No Fabric meter applies to LLM provider traffic on the Free plan. You pay your model provider at their list price, and Fabric adds routing, policy, limits and cost visibility on top.
Cost controls show and cap what is spent. To lower the cost of each request as well, use Adaptive Model Routing, Lightyear and MCP Tool Search on the same routes.
Connect your first model, MCP server or internal API and apply consistent governance from one gateway.