Urgent.News

What's breaking now, across thousands of outlets.

AI

Agentic AI vs Generative AI Examples: Cost Verdict

These agentic ai vs generative ai examples show that one-shot generative tasks are the cheapest way to produce a given amount of text, while an agent loop re-reads its context every step and can cost many times more for the same answer. Verdict: generate with one-shot calls, decide with agents, and run agent loops on the cheap-input models (GLM-5.3 FlashX, Claude Haiku 5.5). In the loop example…

The article compares the costs of generative and agentic AI models by breaking down their token usage and pricing. Generative AI models, like Claude Haiku 5.5 and GLM-5.3 FlashX, charge a fixed rate per token for both input and output. For instance, generating five product descriptions costs $0.31 on Claude Haiku 5.5 and $0.008 on GLM-5.3 FlashX.

In contrast, agentic AI models, which involve re-reading context and iterating on steps, incur higher costs due to the growing context and repeated processing. A 30-step research agent using Claude Opus 5.5 costs $0.96 per run, compared to $0.078 on GLM-5.3 FlashX, a 12.3x price difference.

The cost calculation formula remains consistent across examples: (input tokens x input price) + (output tokens x output price), both per million tokens. Prices vary based on model, with cheaper options like GLM-5.3 FlashX and Claude Haiku 5.5 offering significant savings. For instance, reading a 1M-token corpus is primarily driven by input price.

Mixed pipelines combining generative and agentic layers can reduce costs further. For example, summarizing 100 support tickets with a generative model and then using an agentic model to triage refunds results in a total cost of about $0.18 (Rs 17.26). Using GPT-6.1 Terra Pro for both layers would cost significantly more at $1.10.

To perform these calculations yourself, simply count the tokens for your specific task, including prompt, context, and output, then multiply by the respective input and output prices for the chosen model.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in AI

AI Support Automation: A 16-Case Ticket Lifecycle Test Before Launch

AI support automation can reopen the wrong ticket: test the lifecycle before launch If an AI feature can create, update, resolve, or reopen service tickets, evaluate it as a state-changing…

  • Test AI ticket automation's full lifecycle to prevent unintended consequences.
  • Verify system distinguishes drafts from authorized transitions and updates tickets correctly.
  • Test each operation individually to avoid concurrency issues and unintended state changes.

More from Thursday 5 November →