Frameworks

ArmorIQ ships a first-class integration for Google ADK — one line wraps the root agent and every tool call routes through the ArmorIQ loop. For every other framework, use the raw-client pattern: call ArmorIQClient directly from inside your tool wrapper. Ten lines of glue code, works with anything.

Support matrix

🔧 Raw client means the SDK doesn't ship a framework-specific wrapper — you write a tiny adapter (about 10 lines) that calls client.invoke() from inside your existing tool. The approach is the same across every framework; examples for the common ones are on the Custom frameworks page.

How integration works at a high level

Every framework has somewhere to intercept tool calls before they hit the network:

• Google ADK — before_tool_callback / after_tool_callback on the Agent.
• CrewAI — subclass BaseTool, override _run().
• LangChain — subclass BaseTool, override _run().
• OpenAI Assistants — the function_call step in your run loop.
• Anthropic — tool_use blocks in the response stream.

In each case you insert the ArmorIQ three-step flow:

capture_plan → get_intent_token → invoke

The ADK integration wires all three hooks for you automatically. The raw-client pattern asks you to wire them yourself — it's more verbose but works everywhere.

Which page should I read?

Roadmap

First-class integrations for additional frameworks are planned. Watch the changelog for:

• CrewAI — drop-in ArmorIQCrew(agents=..., tasks=..., armoriq_client=...) wrapper.
• LangChain — ArmorIQAgentExecutor with automatic tool wrapping.
• OpenAI Assistants — run-loop middleware.
• Anthropic tool-use — response interceptor.

Until those ship, the raw-client pattern is the recommended integration path.