Go-To-Market
Live price monitoring with eve agents
In this example, an eve agent uses the @nimble-way/eve extension to read competitors' pricing pages. Name a competitor in Slack and the agent finds its official pricing page with Nimble Search, reads it with Nimble Extract, and saves the plans to Postgres. Every morning an eve schedule reads each tracked page again, application code compares the result with the last snapshot, and only a real change reaches the channel, with the page link and the time it was read. Replies in an alert's thread continue the same eve session.
Quick Start
Inputs
- Competitors A name in Slack, such as "track Postmark", or a pricing page URL. Nimble Search finds the official page from a name.
- A Slack channel Where alerts go, connected through Vercel Connect.
- A schedule A cron in one eve schedule file, 13:00 UTC by default.
Outputs
- Sourced change alerts in Slack: competitor, plan, old value, new value, page link and read time
- A Postgres history of every pricing page read
- Thread answers about any tracked plan, read live
- A labeled demo pricing page (Acme Mail) whose price changes on command, for seeing an alert end to end
How it works
A 5-step loop, from a Slack mention to a sourced alert.
- Track from Slack A mention like "track Postmark" sends Nimble Search to find the official pricing page. Nimble Extract reads it and the plans are saved as the baseline.
- Check on a schedule One file in agent/schedules/ is a Vercel Cron Job. It starts an eve session in the alerts channel, and the agent reads every tracked page again with Nimble Extract.
- Compare in code The model passes the plans it read to a tool as typed fields. Application code normalizes them, stores a snapshot in Postgres and compares it with the last one. The model never decides whether a price changed.
- Post only real changes Prices, billing periods, limits and plans added or removed trigger one Slack message with sources. Otherwise the agent calls eve's no_reply tool and posts nothing.
- Ask in the thread A reply to an alert continues the same eve session. The agent reads the page again with Nimble Extract and answers with the link.
Stack
Nimble primitives plus the full runtime stack.
Nimble APIs
What it does
- @nimble-way/eve The eve extension that mounts Nimble's tools in the agent. Its Web Search Agent tools are disabled here.
- search Finds each competitor's official pricing page, and finds it again when it moves.
- extract Reads the rendered pricing page as clean markdown, on tracking, on every daily check, and on thread follow-ups.
3rd Party Tools
Role
- eve 1.0 Schedule, Slack channel, durable sessions and the no_reply tool.
- anthropic/claude-sonnet-5.5 Through Vercel AI Gateway: reads plans into typed fields and writes the alert.
- Postgres (Neon) Competitors and daily snapshots, created on first use.
- Vercel Hosting, Cron Jobs, Connect for Slack, and Blob for the demo page's price.
- TypeScript, Node.js 24 The agent's language and runtime.
Reach out if you have any questions.
Talk to an Expert