Jev email intent workflow

A smoke check. The README states the ten labelled examples are not an accuracy benchmark, and the set is deliberately awkward: two of the general emails mention invoices. Expected labels are used only for evaluation and never sent to Jev. The tests mock the SDK response and verify routing and input isolation, not semantic accuracy.

No. The input emails are mocked and the handlers only set a destination in graph state; they do not send email or make payments. Confidence is exposed for inspection, but this demo always routes to one of the two handlers rather than abstaining.

Execution stops rather than assigning a fabricated intent, and each output line carries intent, confidence, both label probabilities, destination, model and a comparison against the expected label. No retry or degraded-mode path is documented.

Yes. Call await build_workflow(client).ainvoke({"email": email}) with an email containing id, sender, subject and body, while the async client is still open. Setup needs Python 3.10+ and uv, a .env holding TYPESAFE_API_KEY, and it makes one real API call per email. The default model is jev-1.12, overridable with TYPESAFE_DEFAULT_MODEL.

Python 3.10+ and uv. Run uv sync, put TYPESAFE_API_KEY in a .env while keeping any existing one, then uv run python main.py to process the set, or uv run python main.py --email-id email-09 for one. Classification makes one real TypeSafe call per email, and the default model is jev-1.12, overridable with TYPESAFE_DEFAULT_MODEL.

data/mock_emails.json holds five invoice requests and five general emails, and two of the general ones mention invoices on purpose. invoice covers invoice delivery, copies, corrections, disputes and payment follow-ups; general is the catch-all. Expected labels are used for evaluation only and are never sent to Jev.

The repository ships no license file, so the reuse terms are unclear from the source itself, and that is worth resolving before you build on it. Everything the README describes is behavior rather than permission, so treat the code as readable for reference until a license appears.