Loading pattern preview
BlocksTools & Utilities
Jev Email Tags
Jev Email Tags
Tag a closed inbox with one Jev boolean per tag. A stamp lands only when its probability clears a floor.
Use this when you are multi-label tagging a known set of messages, such as an inbox, without writing a classifier prompt or allowing invented labels.
Loading pattern preview
Problems solved
Technical challenges this implementation handles out of the box.
- Tag a closed inbox with one boolean per tag
- Keep the tag floor in application code
- Leave untagged mail unmarked instead of inventing labels
Use cases
Products and workflows this pattern is designed to support.
- Multi-label tags on a known inbox
- Stamping mail without a classifier prompt
- Teaching Jev boolean probabilities across many items
Compare with
Similar patterns, and when each one is the better fit.
Jev Search FilterFreeUse this when you want semantic search over a known catalog, such as emoji or icons, without building embeddings, scoring each item with a boolean.
Jev Action GateFreeUse this when you are deciding whether to auto-approve one proposed action at a time, using a single Jev probability against a floor you control.
Jev Best-of-N JudgeUse this when you already have several candidate replies to one prompt and need one chosen, or none at all if the pick is too close to call.
Jev Infinite FAQUse this when FAQ visitors ask in their own words and you want to open the matching canned answer or add a grounded answer as a new row.
Setup
Requirements, wiring steps, and what this pattern adds to your project.
Getting started
Pick how you want to pull this pattern in. Then wire env vars and routes the same way.
- 1
Download → Next.js app
Use Download → Next.js app in the preview toolbar. You get a zip scaffold (Pro downloads rewrite preview `/view/.../api/*` paths to `/api/*` automatically).
- 2
Extract the zip and install dependencies
Unzip the archive, then run `pnpm install` (or npm / yarn) in the project folder.
- 3
Fill .env.local
The download includes .env.local placeholders when needed. Add real values for: AI_GATEWAY_API_KEY.
- 4
Customize the agent and tool files
Adapt prompts, tools, and stop conditions in the generated project for your product.
- 5
Run the app and open the pattern route
Run `pnpm dev`, open the setup/checklist page if present, then navigate to the generated pattern route and verify responses.
Environment variables
AI_GATEWAY_API_KEYGet key
Capabilities
AI SDK APIs
experimental_evaluateProviders
Jev
External services
gatewayvercel-ai-gatewayUpstash
Files added
13 files
app/page.tsxapp/layout.tsxapp/api/tag/route.tscomponents/inbox-tags-demo.tsxcomponents/inbox-list.tsxcomponents/typesafe-ai.tsxhooks/use-inbox-tags.tslib/inbox.tslib/tag-questions.tslib/tag-policy.tslib/rate-limit.tslib/request-utils.tsREADME.md
Dependencies
7 total
npm packages
6UpstashAISDKlucide-reactmotionNext.jsReact
Registry components
button
Critical files
4 files
lib/tag-policy.tsPure decideTags policy: keep a message/tag pair only when P(tag) >= 0.70. A missing answer stays off the row. Do not call Jev from unit tests. Use Experimental_EvaluationMockModelV4.
lib/tag-questions.tsbuildTagQuestions writes one boolean per inbox message and closed tag. TAG_FLOOR is 0.70 and stays in application code.
lib/inbox.tsClosed inbox and tag set. Jev may only answer these ids. Do not let the model invent messages or tags.
tag/route.tsRate-limited experimental_evaluate call through AI Gateway model typesafe-ai/jev with zeroDataRetention. The inbox is not in the request. Returns decideTags hits, never a free-text label list.
Requirements
- Complexity
- Beginner
- Setup time
- ~5 minutes
- Node
- 24+
- Memory
- 256MB
Upstash Redis for deployed demo rate limiting
