Pick the tool you already run. Most integrations attach TrustGuard at the request. Some also send MCP traffic through TrustGate. A few coding-agent plugins do both.
allow, report, transform, ask, or block. The host enforces the verdict.TrustGateRoutes model and MCP traffic, with shared credentials and policy.AI coding agents
Developer tools that read repositories, run commands, and call tools. TrustGuard evaluates their lifecycle events; TrustGate serves their MCP tools.
Agent platforms
Organization-managed AI services, administered centrally for users and connectors.
AI gateways
Policy on model traffic that already passes through a gateway, with no change to each client.
Agent frameworks
Checks at the agent, workflow, or tool boundary of the code you write.
Observability
Trace the calls your application sends through TrustGate in the tool you already use.
Build your own
SDKs, middleware, and the REST API, for custom applications and platforms without an integration.
How TrustGuard integrations work
Most TrustGuard integrations call the evaluate API. TrustGate uses a native connection and does not require a collector API key.direction to "input" before the model call and "output" after it. TrustGate
sets the direction automatically. See the Evaluate API
for the full contract.
Create the API key from Agent Security → Collectors → Catalog in the console. The
selected collector also provides setup
instructions and a configuration snippet.
Create the policy in Observe mode. Observe records decisions in Activity
without enforcing them. Review the results, then switch the policy to Enforce.
See Policies.