Hono's author routes HTTP by meaning, then warns you not to
Yusuke Wada published hono-jev-router, an experimental Hono router that asks Jev which plain-language description matches an incoming request. The README treats it as a demo with sharp limits.
Yusuke Wada, maintainer of Hono, released hono-jev-router: an extension allowing route registration by description, such as app.on('jev', 'a request from an AI agent', handler). The router forwards request metadata, including method, URL, headers, and a truncated body, to Jev as parallel Noul (boolean) questions. The first description whose probability meets the configured threshold (defaulting to 0.5) handles the request.
The repository README outlines several operational limits. The author warns against using semantic routing for authentication, since request payloads could manipulate matching. Authorization and Cookie headers are redacted, but other request data is sent externally. Because every semantic route incurs API usage, the author recommends rate limiting. Standard path routes take precedence, allowing endpoints like /health to resolve without model calls.
On X, Carlos Alberto shared the project alongside TypeSafe’s official skill file and OpenRouter listing as a deploy kit for Cloudflare Workers. The router supports calling TypeSafe directly or through c.env.AI.run('typesafe/jev').
Because Noul queries evaluate independently, their probabilities do not sum to 1. The documentation notes this distinction compared to selecting a single option via Choice.
This site's reading
Editorial notes evaluating claims against primary sources, contextualizing findings alongside related implementations, and defining technical terms.
Verify
The GitHub README corresponds with the post details: hono-jev-router is published, Yusuke Wada is the author, and example code registers routes via app.on('jev', '<description>', handler). TypeSafe's skill file resides in a separate official repository (typesafe-ai/skills) advising coding agents to consult current documentation. We did not run or send traffic to the router. The security cautions are stated directly by the author in the README.
Compare
While browser and game demonstrations constrain Jev to an action list generated by software, this router matches requests against plain-text descriptions supplied by the developer. It uses parallel Noul queries (evaluating each description as an independent boolean question) rather than a single Choice call over routes. As noted in the README, the resulting probabilities do not sum to 1. Standard path-based routes take precedence, ensuring endpoints like /health resolve without invoking the model.
Terms
- Semantic route
- An HTTP route handler matched by a descriptive phrase (such as 'a request from an AI agent') instead of an exact method and URL path.
- Noul
- TypeSafe's boolean primitive. This router submits one Noul query per registered description within a single request, returning probabilities between 0 and 1.
- Threshold
- The minimum score required for a match (defaulting to 0.5). The first description whose Noul probability exceeds this value triggers its handler.
- Skill file
- A SKILL.md instruction file read by coding agents. TypeSafe's file prompts agents to fetch updated documentation rather than relying on stale parameters.