Agents Lookup

Use cases / Decision models (Jev)

Filter database records by meaning, not exact values

Ask Jev a yes/no question per record, such as whether a role could be remote, to filter a database or list by meaning.

DifficultyIntermediate
Setup time2-4 hours
CategoryDecision models (Jev)

Author's figure: Author's figure: 129 rows, roughly 1 s (Zachi). Reported by the builder, not measured by us.

The use case

Teams sitting on tables of companies, people, notes or todos often want filters that no column supports: which roles could work from home, which notes mention a stalled deal, which companies sell to schools. These builds pass each candidate record to Jev with a yes/no or Choice question and keep the ones that pass, sometimes after a cheap keyword or embedding step narrows the list. It is slower than an index, so it suits hundreds to low thousands of rows per query. A person checks results before acting on them, especially for anything about people.

Example workflow

  1. Narrow candidates with SQL or embeddings in Postgres
  2. Pass each remaining record's text to Jev with the filter question
  3. Keep records above a probability threshold
  4. Show results with their probabilities in Metabase or a sheet
  5. A person reviews the list before acting on it

Tools

Risks and guardrails

Sources

Written by Agents Lookup. Credits and official pages for the tools this use case names: