Invarix.Gate.Extensions.AI
1.0.0-rc.1
dotnet add package Invarix.Gate.Extensions.AI --version 1.0.0-rc.1
NuGet\Install-Package Invarix.Gate.Extensions.AI -Version 1.0.0-rc.1
<PackageReference Include="Invarix.Gate.Extensions.AI" Version="1.0.0-rc.1" />
<PackageVersion Include="Invarix.Gate.Extensions.AI" Version="1.0.0-rc.1" />
<PackageReference Include="Invarix.Gate.Extensions.AI" />
paket add Invarix.Gate.Extensions.AI --version 1.0.0-rc.1
#r "nuget: Invarix.Gate.Extensions.AI, 1.0.0-rc.1"
#:package Invarix.Gate.Extensions.AI@1.0.0-rc.1
#addin nuget:?package=Invarix.Gate.Extensions.AI&version=1.0.0-rc.1&prerelease
#tool nuget:?package=Invarix.Gate.Extensions.AI&version=1.0.0-rc.1&prerelease
Invarix.Gate.Extensions.AI
Microsoft.Extensions.AI adapter for Invarix.Gate, the deterministic action firewall for AI agents on .NET.
dotnet add package Invarix.Gate.Extensions.AI --prerelease
using Invarix.Gate;
using Microsoft.Extensions.AI;
var gate = GateEngine.Create(GateOptions.FromYaml("gate-policy.yaml"));
var client = innerClient.AsBuilder()
.UseInvarixGate(gate, agentId: "checkout-bot")
.Build();
One call installs both attachment points: every tool call goes through the policy
engine before it executes, and the chat boundary is tapped for token usage, so per-run
and per-agent ceilings see spend as it happens rather than after the run. MCP client
tools are covered through the same interception point, because they are ordinary
AIFunctions.
UseInvarixGate replaces UseFunctionInvocation(). A pipeline that registers both is
rejected at build time, because a second function-invoking client would execute tool
calls Gate never sees.
Gate covers the tools invoked through the wrapped pipeline; the run report publishes
what it could not see. docs/COVERAGE.md in the Invarix.Gate package states the
boundaries in full.
License
Observe mode is free under the Elastic License 2.0 and blocks nothing. Enforce mode and approval workflows require an Invarix.Gate Professional license: invarix.dk/gate.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net8.0 is compatible. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. net9.0 was computed. net9.0-android was computed. net9.0-browser was computed. net9.0-ios was computed. net9.0-maccatalyst was computed. net9.0-macos was computed. net9.0-tvos was computed. net9.0-windows was computed. net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net10.0
- Invarix.Gate (>= 1.0.0-rc.1)
- Microsoft.Extensions.AI (>= 10.0.0 && < 12.0.0)
-
net8.0
- Invarix.Gate (>= 1.0.0-rc.1)
- Microsoft.Extensions.AI (>= 10.0.0 && < 12.0.0)
NuGet packages (1)
Showing the top 1 NuGet packages that depend on Invarix.Gate.Extensions.AI:
| Package | Downloads |
|---|---|
|
Invarix.Gate.AgentFramework
Microsoft Agent Framework adapter for Invarix.Gate, the deterministic action firewall for AI agents on .NET. One call, agent.AsBuilder().UseInvarixGate(gate).Build(), routes the agent's tool calls through Gate's permission envelope before they execute. Token accounting needs the chat boundary tapped, and Agent Framework's builder cannot install that: wrap the IChatClient with UseInvarixGate from Invarix.Gate.Extensions.AI before constructing the agent. At attach time this package enumerates the agent's registered tools and warns about any that cannot be intercepted, so a wiring mistake surfaces at startup instead of during an incident. Observe mode is the default and blocks nothing. |
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 1.0.0-rc.1 | 70 | 8/6/2026 |