The orders table grew from ~82k to 340k items in the last 12 hours, well above the 6k/day baseline. Change Events show a bulk backfill started at 02:14 UTC. Your dbt models in the warehouse have not refreshed since yesterday and are now serving yesterday's numbers.
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.
An agent does what you'd do, and only what you've authorized.
It acts on the same governed metrics as your dashboards, and every action is logged and traceable.
It alerts and recommends on its own; anything that changes data is yours to approve.
Point a new agent at a throwaway channel and watch its judgment before it touches anything real.
It remembers what it already flagged and waits before acting again, so it won't alert you about the same thing twice.
It compares item counts and key distributions in your DynamoDB tables against what landed in the warehouse, flags gaps or duplicates before your dbt models run on stale data, and surfaces the discrepancy so you can fix the pipeline instead of debugging a dashboard.
When Change Event throughput drops or a shard falls behind, it tells you which tables are affected and how far behind the warehouse has drifted, so you can intervene before the lag becomes a data quality incident your stakeholders notice first.
DynamoDB is schemaless, so new attributes show up without warning. The agent scans Items for attributes your pipeline does not expect, flags the change with the table and approximate time window, and routes it to you before it breaks a downstream model.
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.
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:
Every Amazon DynamoDB object, modeled and query-ready the moment you connect.
It runs on your real DynamoDB account (schemaless sprawl, hot partitions, test tables and all), not a tidy demo.
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.
A payload to your own systems, to wire the agent into whatever you already run.
A flag written back to your warehouse for everything downstream to pick up.
Kick the question to Fi to investigate the why and propose the fix.
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.
Fi is your AI analyst. It helps you build and customize everything in Definite, including the agents that watch and act.
Your AI analyst. Ask questions in plain English, and let it help you build and customize everything in Definite, including your agents.
Meet Fi →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 →