A8gent

Reference

AI automation glossary

101 terms defined in plain English, for the moment a vendor, a developer or a documentation page uses a word you were not going to admit you did not know. Every entry explains what it is, how it works, what it costs and what to watch for - with a link to the primary source and the month we checked it.

How to use this glossary

Most of the confusion in AI automation is vocabulary rather than difficulty. A vendor says their product does tool calling and you cannot tell whether that is a real capability or a rebranded webhook. A platform quotes a price per operation and a competitor quotes per execution, and the two numbers are not comparable. Someone asks whether your automation has guardrails and you would like to answer with something more specific than yes.

These pages are written for that. Each one gives a one-sentence answer at the top, then the detail underneath: how the thing actually works, what it costs, where it goes wrong, and what a business should do about it. They are longer than a dictionary entry on purpose, because the short version is the part that leaves you unable to ask a follow-up question.

Use it in reverse before a sales call. Read the vendor's page, list every term you could not define crisply, and look those up first - they are exactly where scope confusion and overselling hide. If you would rather someone else did the translating, the free AI automation audit maps your workflows and says plainly which of them are worth automating, and our automation services cover the build and the handover.

Anything that moves - prices, throughput limits, plan mechanics, regulation - is dated on the page it appears on, and every entry links to the specification, vendor documentation or regulator it came from so you can check it yourself. Where a figure is genuinely unknowable from someone else's data, the page says so and shows you how to measure your own instead.

What to learn first, if you are starting from zero

An alphabetical list is the right shape for looking something up and the wrong shape for learning. If you are new to this, read these in order. Each one is hard to understand until the one above it makes sense, and together they cover about eighty percent of what appears on a vendor call.

  1. 1. Workflow automation, then AI agent. Start with the older idea. Workflow automation is a fixed sequence someone wrote down; an agent decides the sequence at runtime. Almost every argument about what AI can do for a business is really an argument about which of these two you need, and the boring one wins more often than the industry admits.
  2. 2. Tool calling. This is the mechanism that turns a model that writes text into something that changes the state of your business. Once you understand that the model is only choosing which function to run and with what arguments, most of the mystique disappears and the right questions get much easier to ask.
  3. 3. Token and context window. The unit your model bill is denominated in, and the limit on how much the model can consider at once. These two explain both why the invoice moved and why the agent forgot something you told it earlier.
  4. 4. RAG. How an agent uses your documents. Read embedding, chunking and vector database straight after, as one sitting. They only make sense together.
  5. 5. Hallucination, guardrails and human in the loop. What goes wrong, what you do about it, and where a person stays in the chain. This is the trio that decides whether an automation is safe to point at a customer.
  6. 6. Execution versus task versus operation. The commercial one. Learn this before you compare two prices, because until you have, you are not comparing two prices. The AI agent platform directory has a full billing-unit table built on it.
  7. 7. ROI and payback period. Last, not first, because they need the six above to be filled in honestly. Once you can estimate the running cost, these two tell you whether to proceed.

Read as prose rather than as definitions, that sequence is roughly the learn hub, starting with what an AI agent is. If you would rather learn it with something being built alongside, the courses cover the same ground in order, and the build guides assume you already have it.

Agent concepts

What an agent is, how it decides what to do next, how it reaches your systems, and the controls that stop it doing something expensive.

This is the group where the marketing pressure is highest, so it is the group worth reading properly. The terms here divide into three jobs. Some describe how the model thinks: context window, token, temperature, system prompt, ReAct, planner-executor. Some describe how it reaches the outside world: tool calling, function calling, MCP, A2A. And some describe how you stop it being wrong in a way that costs money: guardrails, evals, observability, human in the loop, prompt injection. A vendor who is fluent on the first group and vague on the third is selling a demo.

The retrieval terms - RAG, embedding, chunking, reranking, vector database - belong together and are almost always encountered as a set. They are the answer to one question: how does an agent use documents it was never trained on. If a vendor tells you their agent knows your business, this is the machinery they are describing, and knowing the vocabulary lets you ask which part of it they actually built.

37 terms

Automation mechanics

How automation platforms actually work: triggers, integrations, the billing units they charge in, and what keeps a workflow reliable when a step fails.

Nothing here is glamorous and all of it decides whether an automation survives its first bad week. Two clusters matter most commercially. The first is metering: execution versus task versus operation is the term that makes two quotes comparable, and without it a $9 plan and a $50 plan tell you nothing. The second is reliability: error handling, retry and backoff, idempotency, queues and rate limits are the difference between a workflow that recovers from an outage and one that quietly sends the same invoice four times.

The connection terms - API, REST API, GraphQL, webhook, polling versus webhook, OAuth, API key, JSON, data mapping - are what an integration is actually made of. You do not need to write any of it, but knowing whether a platform reaches your system by webhook or by polling every fifteen minutes tells you how fast your automation can possibly be, and that is a question worth asking before you buy rather than after.

38 terms

Voice and messaging

The terms that appear the moment an automation starts phoning or texting customers, including the US compliance vocabulary.

Voice has its own physics. Speech to text, text to speech and latency budget describe the chain a spoken sentence travels through, and barge-in and DTMF describe the two things callers do that break naive implementations: talking over the agent, and pressing keys. If a demo never shows an interruption, it has not shown you the hard part.

The messaging half is compliance rather than engineering. A2P 10DLC registration, opt-in and STOP handling are legal requirements in the United States, not features, and they apply to you rather than to your vendor. Missed-call text-back is the single highest-return pattern in this group for most service businesses, and it needs all three of those terms understood before it goes live.

12 terms

Business and buying

The numbers an owner uses to decide whether an automation is worth having, plus the contract and data questions that come up before anything touches live data.

These are the terms that decide whether a project happens. ROI, payback period and total cost of ownership are the frame; cost per booked job, lead response time, speed to lead and no-show rate are the operational numbers that actually move, and they are the ones worth measuring for a fortnight before you automate anything so you have a baseline to argue from afterwards.

The rest of this group is the paperwork that appears once something is going to touch live data: DPA, data residency, zero data retention, SLA, vendor lock-in, proof of concept and handover. Handover is the one most often skipped and most expensive to skip. If you cannot say who owns the workflow, the credentials and the documentation at the end of a project, you have not bought an automation, you have rented one.

14 terms

Concepts that get confused

Four pairs account for most of the misunderstanding in this field. In each case the two things are used interchangeably in marketing copy and are not interchangeable at all, and in each case the confusion has a price attached.

Agent vs workflow vs automation

Workflow automation runs a sequence a human wrote down: when this happens, do these five things, in this order, every time. An AI agent is given a goal and a set of tools and decides the order itself, which is why the same input can produce different paths on different runs. An agentic workflow is the middle ground most real systems land on: a fixed skeleton with a model making judgement calls at two or three specific points.

Commercially this is the most expensive distinction on the page, because non-determinism is a cost, not a feature. A fixed workflow can be tested once and trusted. An agent has to be evaluated continuously, needs observability to debug at all, and will occasionally do something reasonable that you did not want. Pay for that flexibility where the work genuinely varies, and refuse to pay for it where it does not. A large share of disappointing AI projects are agents doing a job a workflow would have done more cheaply and more reliably.

RAG vs fine-tuning

RAG retrieves relevant text at the moment of the question and puts it in front of the model, so the model has never seen your data before and does not need to. Fine-tuning changes the model's own weights by training it on examples, which shifts how it behaves rather than what it knows.

The rule of thumb worth remembering: RAG for knowledge, fine-tuning for behaviour. If the complaint is that the agent does not know your pricing, your policies or your product catalogue, that is retrieval, and retraining a model will not fix it while costing considerably more. If the complaint is that the agent knows the right answer but says it in the wrong voice, at the wrong length or in the wrong format, fine-tuning is the lever, though a better system prompt usually gets most of the way there for nothing. Distillation is a third thing again: making a smaller, cheaper model imitate a larger one, which is a cost play rather than a capability one.

MCP vs function calling vs plugins

Function calling is a model capability: the model emits a structured request naming a function and its arguments, and your code decides whether to run it. It is the underlying mechanism, and it is provider-specific in its details. MCP, the Model Context Protocol, is a layer above that: an open standard for how an AI application connects to external tools and data sources, so that a connector written once works across the clients that support it. Its own documentation describes it as a USB-C port for AI applications, which is a fair summary of the ambition. Plugins, in the older sense, were the vendor-specific version of the same idea, and they did not travel between products.

The distinction that matters when buying: function calling ties your integration to one model provider's conventions, while an MCP server is portable across the clients that speak it. That is a vendor lock-in question rather than a technical one. Worth knowing alongside it, A2A solves a different problem again: MCP connects one agent to its tools, A2A lets separate agents discover each other and delegate work across frameworks. They are complementary rather than competing, and a vendor who treats them as alternatives has not read either specification.

Orchestration vs choreography

Both describe how several moving parts coordinate, and they are opposites. In orchestration there is a conductor: one component holds the plan, calls each step and knows the overall state. That is what a planner-executor setup does, and what most visual automation platforms are. In choreography there is no conductor: each component reacts to events it cares about, usually through a queue or a webhook, and the overall behaviour is emergent. Most multi-agent systems are a mix.

The commercial consequence is debuggability. An orchestrated system has one place to look when something goes wrong and one place to enforce guardrails. A choreographed one scales better and fails in ways that are much harder to trace, because no single component knows what was supposed to happen. For a business automating a process rather than building a platform, orchestration is almost always the right answer, and the distinction is worth raising with anyone proposing the other.

Common questions

Which terms should I learn first?
Six of them, in this order: AI agent, workflow automation, tool calling, token, RAG and human in the loop. Together they let you read almost any vendor page and tell what is actually being sold. Everything else in this glossary is detail hanging off one of those six. If you would rather have it as a narrative than as definitions, the learn hub covers the same ground as prose, and the courses walk through it with something being built alongside.
Is an AI agent the same thing as a chatbot?
No, and the difference is what it can do rather than how it talks. A chatbot produces text. An agent produces actions: it calls tools, writes to your systems and changes the state of something. A chatbot that answers a question about your refund policy is a chatbot. One that looks up the order, checks the policy and issues the refund is an agent, and the second one needs guardrails, an audit trail and usually a human review point that the first one does not.
Do I need to understand any of this to buy automation?
Not all of it, but the billing vocabulary pays for itself immediately. Knowing the difference between an execution, a task and an operation is the difference between a quote you can compare and a quote you cannot. So does knowing what a webhook is, because it decides whether your automation reacts in seconds or in fifteen-minute polls. The rest you can safely look up when a vendor uses it and you want a follow-up question ready.
How current are these definitions?
Every entry carries the month it was checked and links to the specification, vendor documentation or regulator it came from, so you can verify it rather than trust it. The fast-moving parts are prices, plan mechanics, throughput limits and messaging regulation, and those are dated on the page they appear on. Where a figure genuinely cannot be known from someone else's data, the entry says so and shows you how to measure your own instead.
What is the difference between the glossary and the learn hub?
The glossary answers what a word means when you hit it mid-sentence. The learn hub answers how the ideas fit together and why they matter, at the length of an article rather than a definition. Use the glossary in the middle of a vendor call or a documentation page, and use learn when you have an hour and want the shape of the whole thing. The build guides are the third layer: they assume both and get on with wiring something up.
Why do the same words mean different things on different vendor sites?
Because most of them are unregulated marketing terms rather than defined ones. Agent, workflow, orchestration and credit are all used loosely, and a credit in particular means whatever the vendor decides it means: a row of output on one platform, a second of compute on another, an action weighted by complexity on a third. Where a term has a real specification behind it, such as MCP or A2A, the entry links to it. Where it does not, the entry says so plainly.
Which of these terms actually affect the price I pay?
Six do most of the work. Execution versus task versus operation decides how your volume is metered. Token decides your model bill. Polling versus webhook decides how many wasted runs you pay for. Rate limit and retry and backoff decide how much duplicated work a bad afternoon produces. Self-hosting decides whether you pay a subscription or a server. Total cost of ownership is the one that ties them together, and it is the number worth building before you sign anything.
Can I use these definitions in my own documentation?
Yes, with a link back. They are written to be quoted: each entry opens with a one-sentence answer that stands alone, and the sources are cited so whoever reads your document can check them too. If you need the same material shaped around your own systems rather than in general, the free automation audit produces exactly that as part of its write-up.