Generative AI produces content. Agentic AI uses that ability to pursue a goal across systems, deciding and executing a sequence of actions along the way. The practical difference is what each is judged on: a generative system is judged on its output, an agentic system on the end state it reaches.
Producing an answer versus reaching an outcome
A generative system is judged on its output. Was the summary accurate, was the draft usable, was the classification right. The interaction is bounded: input goes in, output comes back, a person decides what to do with it.
An agentic system is judged on the end state. Did the ticket get resolved, did the records reconcile, did the order reach the right team. It may call a model several times along the way, but the model is a component rather than the product.
What gets harder
Errors compound. A generative system that is right nine times in ten gives you one bad answer to catch. An agent that takes six steps at that accuracy finishes correctly just over half the time. Reliability has to be engineered at the loop level — through validation between steps, retries with different approaches, and checks that catch a bad intermediate result before it becomes an action.
State becomes real. A chat exchange leaves nothing behind. An agent writes to systems, and a half-finished run leaves the business in an in-between state. That needs the same thinking any distributed system needs: idempotent operations, a record of what was done, and a way to unwind.
Cost stops being predictable. One request, one response, one price is easy to forecast. A loop that runs until it succeeds is not, unless you cap it.
What stays the same
Both depend entirely on the quality and reachability of your data. A model that cannot see the current state of an account will guess, and an agent that guesses acts on the guess. Retrieval, permissions and freshness matter in both cases; they simply matter more when the output becomes an action.
Both also need evaluation against real examples rather than impressions. The method is the same — a fixed set of cases, a defined notion of success, and a run on every change.
Choosing between them
If a person will review the output before anything happens, generative is usually enough, and it is the cheaper and more predictable choice. If the value only appears when the work is actually completed — and a person reviewing every case would remove that value — the agentic pattern is what you need.
Many useful systems are both. A generative layer drafts and explains; an agentic layer handles the routine cases end to end and escalates the rest. Deciding which cases belong in which half is the real design work.
