Skip to content

Docs

Competitor Monitor with Jev

An official Mastra template that checks pricing, changelog, and documentation pages against saved captures, has Jev classify each change with its evidence, and routes it to ignore, record, request review, or alert.
Format
Docs
Reading time
2 min
Published by
Community
Author
Mastra
Last verified
Oct 2026

Highlights

  • Scaffold with npx create-mastra@latest competitor-monitor --template competitor-monitor-jev --no-install, then npm ci and cp .env.example .env.
  • Two routes to Jev: TYPESAFE_AI_API_KEY with jev-latest by default, or JEV_ACCESS_MODE=vercel-gateway plus AI_GATEWAY_API_KEY for typesafe-ai/jev.
  • Unchanged pages with no pending work skip Jev, each chat request runs one check, and the first successful check saves a baseline instead of reporting changes.
  • Each monitor covers 3 sites by default, MAX_SOURCES accepts 1 to 20, SOURCE_CONCURRENCY=3 controls fetches up to 5, and each competitor needs its own monitorId.
  • The optional scheduler runs daily at 09:00 UTC from scheduled-monitors.json, and only scheduled checks dispatch notifications such as Markdown reports.

Watch out

Official but opinionated: it monitors public English-language pages only, because the template says Jev's accuracy is best in English, and it needs access to openai/gpt-6-luna for the Studio chat plus a TypeSafe or gateway key. Browser fallback is restricted, so sites needing cross-origin resources may not render useful content.

Questions about this entry

Short answers drawn from the linked project or page.

From the Jev guides

Original write-ups on what this entry is for.

From the Jev AI model community

Posts from builders shipping with Jev right now.

Follow @typesafeai