Monitoring and budget
Smart Intelligence — Watchtower-style monitoring plus Budget Butler enforcement that can stop loops, not just email you later.
Official recipe: Watchtower + Budget Butler
Feeds, price trackers, and agent cron jobs love to re-fetch the same URLs every hour. SmartGate shapes monitoring traffic: fetch once cleanly, dedupe when sources overlap, and hard-cap tool spend before a runaway loop shows up on a invoice.
What feels broken
- Dashboard widgets and agents pile duplicate fetches into every turn.
- Budget alerts often fire after tokens are already spent.
- You want certainty, not another passive chart.
How SmartGate shapes it
- Point monitoring at stable sources — gateway fetch returns Markdown-friendly bodies.
- Let budget guard count tool usage and enforce team caps during automated runs.
- Use pipes to chain fetch → guard so enforcement is part of the workflow, not an afterthought.
- Review activity logs after sign-in when you need audit-grade detail.
What you get
- Less noise in context when conditions change.
- Hard bounds aligned with Strategy Amendment: visibility with enforcement.
- FinOps-friendly metering — gateway counterfactual, not host-model list price.
Gateway path after sign-in (for integrators): smart_fetch → smart_budget_guard → smart_pipe
Related roles and scenes
Same gateway, different jobs — pick the path that matches how you work.
- Research and decisionsPersonal scene: search, fetch, dedup, and compress before the model answers.
- MCP for research and decisionsPersona guide: one MCP server entry, then governed research on every question.
- FinOps leadOwn the AI bill: per-team quota, alerts, and audit rows you can sign off on.
- Agent buildersWire one Streamable HTTP MCP endpoint — seven smart_* primitives, one runtime.