AgentKeys uses Jev for automatic agent routing
AgentKeys in the Heima ecosystem uses Jev's confidence scoring to decide where a request belongs, whether it continues the previous topic and which agent should respond, so users no longer pick a bot manually.
The biggest upgrade in AgentKeys isn't another button. It's one less decision you have to make. Say what you need. For clear requests, AgentKeys chooses the relevant agent automatically. No bot menu to work through, no need to learn which assistant handles what before starting. 🧭 That is the value of decision models like Jev: they are built to make fast, structured choices, with confidence scores, rather than generate a long answer just to decide what happens next. ⚡ In AgentKeys, this approach handles the small handoffs behind a conversation: where a request belongs, whether it continues the previous topic, and which agent should respond. Routing and doing the work become separate jobs, so the conversation needs less manual coordination. 🔑 Less selection doesn't mean less control. Routing stays within your permitted channels, and when confidence is low, AgentKeys asks for clarification. 🏠 For a person or family using several agents, the goal is a more intuitive experience: a familiar conversation instead of a collection of tools to manage. We're building AgentKeys in the Heima ecosystem to make agents easier to use in everyday life. Less choosing. More doing. See the update on Github: https://github.com/litentry/agent-terrier/commit/1dc183579374261690a21ba22393b083539adfad