Skip to main content
NeuralTrust integrates with the tools already in your AI stack, including gateways, coding agents, agent frameworks, applications, and edge platforms. Use this catalog to find the supported connection points and setup instructions for each tool.

​
Products

An integration may support TrustGuard, TrustGate, or both. TrustGuard evaluates individual interactions. TrustGate controls how applications and agents reach model providers and MCP servers. Some coding-agent plugins configure both products.

​
Find your tool

​
AI coding agents

Developer tools and managed coding environments that can read repositories, execute commands, and call external tools. A coding agent sends local lifecycle events through a host hook to TrustGuard, while remote MCP tool traffic follows a separate path through TrustGate to approved MCP servers. TrustGuard lifecycle hooks and TrustGate MCP access are separate controls with separate credentials. The events available to TrustGuard and the way each verdict is enforced depend on the coding agent.

​
AI gateways

Gateway integrations apply policy to model traffic that already passes through the gateway, without changes to each client application. An application sends a request through an AI gateway, where TrustGuard evaluates the input before the upstream call and the output on its return path. Input and output enforcement varies by gateway. Buffered responses can be evaluated before delivery when the adapter supports it. Streamed output may be monitor-only after delivery or unsupported, depending on the adapter. Direct provider calls bypass the gateway.

​
Agent frameworks

These integrations connect at the agent, workflow, or tool boundary.

​
Edge / WAF

These integrations run in front of AI endpoints you operate. They inspect the request body on matching routes and return 403 for blocked requests. They do not inspect responses. A request on a configured AI route reaches an edge function, which sends the request content to TrustGuard, blocks or forwards it based on the verdict, and returns the origin response without output inspection. Only traffic that traverses the configured edge route is covered. Request-body limits, runtime limits, and failure behavior vary by provider. Cloudflare · CloudFront · Fastly · Akamai

​
Build your own

Use an SDK, middleware package, or the REST API for custom applications and unsupported platforms.

​
Compare coverage

Enforcement depends on the host platform. A gateway that owns the request body can forward a masked payload, while a provider hook limited to allow or deny cannot. The ask action also requires an interactive client. See Coverage to compare monitoring, blocking, redaction, and approval support for LLM and tool-level traffic.

​
Employee access to third-party AI

For employee access to AI services your organization does not operate, use the browser extension on managed Chrome and Edge. The extension is configured through managed browser policy rather than the collector catalog.

​
How TrustGuard integrations work

Most TrustGuard integrations call the evaluate API. TrustGate uses a native connection and does not require a collector API key.
Set 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 Runtime → 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.