Skip to content

Enterprise deploymentCustomer-hosted or fully managed.Contact salesView pricing

+Integrations · 15

Works with what you already run.

Most integrations are one line: point the client at Intertrace and use a runtime key. Your code, prompts and models stay the same.

The whole change, for most apps:

Swap the base URL and use an itr_rt_* runtime key. Every model call, tool call and MCP request is then decided before it runs, and shows up in Traffic with the reason.

before → after
- base_url = "https://api.openai.com/v1"
- api_key  = OPENAI_API_KEY
+ base_url = "https://intertrace.fly.dev/v1"
+ api_key  = INTERTRACE_RUNTIME_API_KEY   # itr_rt_…

+SDKs & gateways

Swap the base URL; keep your code.

+Agent frameworks

Route every model call a framework makes.

+Coding agents

Guardrails on the agents that write and run code.

+Chat apps

Put self-hosted chat UIs behind policy.

+MCP

Authorize every tool call before it runs.

+Anything else

Speaks OpenAI? It works.

Any client that lets you set an OpenAI-compatible base URL can go through Intertrace. For raw HTTP, see the curl guide in the docs.

+ The AI watching your AI

Connected in minutes.

Get a runtime key, change one line, and watch your first decision land in Traffic.