Vanik exposes compliance logic through multiple surfaces. The architecture document describes three MCP servers (WTO, UK tariff, EU TARIC) and how clients connect using streamable HTTP rather than stdio — so browser and worker runtimes can share the same contract.
Trust at the boundary
The init handshake can carry an
HMAC token
so only configured callers invoke tools. That sits alongside the public
api.akeru.dev routes described in the platform map.
Tools and schemas
Each server advertises tool schemas the model (or orchestrator) uses to plan calls. Vidhi can walk through how those map to Module 3 search strategies on the Vanik side.
Click any highlighted phrase to ask Vidhi about that concept, grounded in the architecture document plus this page’s anchor context.
For the full chat UI (model picker, Gemini unlock), use /vidhi/.