The nightly sync for orders, events, and user_sessions landed 14% fewer rows in DuckDB than the warehouse source. The gap appeared after Wednesday's schema migration and is growing with each load. Flagging for review before downstream models consume stale counts.
How an agent works
An agent watches one thing and acts on it. Not a workflow, just a standing watch that usually does nothing and acts the moment it should.
You stay in control
An agent does what you'd do, and only what you've authorized.
The same trusted numbers
It acts on the same governed metrics as your dashboards, and every action is logged and traceable.
You approve anything that writes
It alerts and recommends on its own; anything that changes data is yours to approve.
Try it on a test channel first
Point a new agent at a throwaway channel and watch its judgment before it touches anything real.
No false alarms
It remembers what it already flagged and waits before acting again, so it won't alert you about the same thing twice.
What you can put an agent on
Tie your DuckDB tables to the warehouse and catch the drift
It compares your DuckDB tables against the upstream warehouse or production database and flags row-count gaps, schema mismatches, and stale syncs before your downstream models consume bad data. So the number in DuckDB and the number in the warehouse are the same, and you find the drift yourself instead of in somebody else's broken dashboard.
Watch a metric off your tables and catch the break
Point it at a metric you care about (conversion rate, order volume, session counts, whatever your tables describe) and it watches on your schedule. When it breaks trend, it tells you which segment moved and by how much, then hands off to Fi to investigate the why across the data it can see.
Catch a schema change before it breaks the pipeline
When a column type changes, a table disappears, or a view definition silently shifts, the agent catches it from the schema catalog and flags the downstream impact before your dbt models or notebooks hit a runtime error. You find out from a Slack message, not from a failed job at 2 a.m.
Run any Python it needs to get the job done
Beyond alerts and write-backs, an agent can run arbitrary Python, so it can do whatever the task actually requires: call an API, kick off a job, reshape the data, or wire into your own tooling. The action space is yours to define.
Why not just build it yourself?
You could rig one of these with a cron job and a Slack webhook in an afternoon. The watching is the easy part. Here's what you'd own forever, and don't, here:
- →The cross-source join: not one tool's data, but it reconciled against the rest of your stack
- →A trusted, consistent metric: the same number your dashboards use
- →The investigation into why, when something fires
- →A full audit trail of everything it did
- →The upkeep, when the schema drifts or the script breaks at 2am
The data it works from
Every DuckDB object, modeled and query-ready the moment you connect.
It runs on your real DuckDB files (Parquet references, half-documented views, tables nobody formally cataloged yet), not a tidy demo. You define the metric once as governed SQL and it watches that.
Where it acts
Slack
A message in the channel you choose, with the context and a button to act on it.
A summary in the inbox of the people who need to see it.
Webhook
A payload to your own systems, to wire the agent into whatever you already run.
Warehouse write-back
A flag written back to your warehouse for everything downstream to pick up.
Hand off to Fi
Kick the question to Fi to investigate the why and propose the fix.
MCP
Expose it to your own agents and tools over MCP, and drive it from your stack.
Run it in your own VPC or fully self-hosted. Everything it does is pure SQL and Python you can inspect.
Build your agents with Fi
Fi is your AI analyst. It helps you build and customize everything in Definite, including the agents that watch and act.
Fi
Your AI analyst. Ask questions in plain English, and let it help you build and customize everything in Definite, including your agents.
Meet Fi →Agents
The watchers and actors. Once you've built one, it runs on its own, keeping an eye on what matters and acting the way you would.
Autonomous agents →Get started
- 1Connect DuckDB, and the sources it needs to reconcile against. Synced and modeled in an afternoon.
- 2See the numbers tie out to what you already trust.
- 3Put an agent on one thing you can't afford to miss. Fi helps you build it.