This glossary explains the words you will hear when you buy, build or evaluate an AI agent, in plain English and without hype. The full A–Z list of terms follows this introduction. If you are short on time, read the six ideas below first: they are the ones that decide whether an agent is useful and safe in a real business.
How should you use this glossary?
Skim the A–Z list when a proposal, a demo or a vendor call uses a word you do not know. Where one of our pages explains an idea in more depth, the term links to it. The sections below are not definitions; they explain how the terms fit together when you are deciding what to buy.
What makes an agent different from a chatbot?
A chatbot talks; an agent acts. Once a model can use tools (look up an order, book a slot, update your CRM), it stops being a question-answering widget and becomes something that changes data in your business. That is why every other idea on this page matters. Our comparison of AI agents and chatbots goes deeper, and AI agent development shows how we scope one.
How does an agent connect to your systems?
Through tools, and increasingly through MCP, the open standard that lets one connector serve many AI clients. The questions to ask are which actions the agent may take, as which user, and with what logging. Our MCP Connector builds these servers with scoped access, sign-in through your identity provider and audit logs.
Where do the agent’s answers come from?
From your own data, if it is built well. RAG retrieves the relevant passages from your documents before the model answers, so the answer is grounded and can cite its source. Chunking, embeddings, vector databases and reranking are the parts that decide how good that retrieval is. The Knowledge Agent is a working example, and you can try the demo.
Who decides when the agent acts?
You do, through guardrails, approval gates and a human in the loop. A sensible launch starts in shadow mode, where the agent’s choices are proposed or logged and compared with your team’s, then moves to approvals, and only then lets it act alone on low-risk steps. The Ops Agent waits for a named person before anything irreversible.
How do you know it works?
With evals: a fixed set of real examples the system is scored against before launch and after every change of prompt, model or data. Without them, “it looked good in the demo” is the only evidence. Our generative AI development work ships an eval suite with every build.
How do you know it is safe?
By attacking it before someone else does. Prompt injection, jailbreaks and data leakage are the main risks for agents that read outside content and hold tools. Red teaming finds them; guardrails and approval gates contain them. The Guardrail and Eval Audit tests an existing AI app this way.
What to do next
- Want to see the ideas working? Each packaged agent has a live demo, listed on the demos page.
- Wondering what it costs? Read how much an AI agent costs, or see every price on the pricing page.
- Not sure where AI fits in your business? Book a free 30-minute call, or start with our AI Opportunity Audit at $490.