--- title: "What is an AI agent vs a chatbot vs automation | Len P. van der Hof" description: An AI agent takes a goal, uses tools, and acts across steps. A chatbot answers a turn. An automation runs a script. Founders need a charter and a review gate before they call anything an agent. image: "https://lenvanderhof.com/media/generated/blog-hero-ai-agent-en-v2.d33563a274c3.wide.webp" --- [AI Systems](https://lenvanderhof.com/en/blog/category/ai-systems/) Research guide # What is an AI agent? A definition founders can use If it cannot refuse a tool call, it is not an agent you can run. It is a demo that can spend money. Len P. van der HofPublished 15 August 20265 min read If it cannot refuse the tool call, it is a demo that can spend. Direct answer An AI agent is a system that takes a goal, uses tools, and acts across more than one step without a human prompting each one. A chatbot answers a turn. An automation runs a fixed script. An agent is only accountable when it has a charter: inputs, outputs, an authority ceiling, and a review gate. Without those, you have a fluent wrapper, not an operator you can put on a roster. ## Key takeaways - Three tests: does it hold a goal, use tools, and continue across steps? - Chatbot = turn. Automation = script. Agent = goal plus tools plus a ceiling. - No charter, no agent. The charter names inputs, outputs, authority, and the human who can fail the work. - SENSE decides where an agent belongs. STACK hardens the repo it lives in. This page only defines the worker. A founder says “we have agents” and usually means one of three different machines. Mixing them up is how a chat window gets production credentials. ## Three tests Ask three questions of the system in front of you. 1. Does it hold a **goal** that survives more than one prompt? 2. Can it **use tools** (files, mail, a browser, a repo, a payment API) without you pasting the output back in? 3. Does it **continue across steps** when a tool returns something messy? If the answer is no, no, no, you have a chatbot. That is a respectable product. It is not an agent. If the answer is no, yes, no, you have automation: a script with a model somewhere in the pipe. Also respectable. Still not an agent. If the answer is yes, yes, yes, you have something that can act. Now the only question that matters is whether anyone wrote the ceiling down. A fourth no is hidden in the yeses. Can it **refuse** a tool call? If it cannot stop, you do not have a worker. You have a fuse. ## Chatbot, automation, agent A **chatbot** answers a turn. You type. It replies. The context window is the memory. When you close the tab, the work is gone unless you saved it. Useful for drafting. Dangerous the moment you paste its output into a tool it cannot see. An **automation** runs a fixed path. Ticket arrives, fields get filled, Slack pings. A model might classify the ticket. The path does not invent a new path. When it fails, it fails in a place you can find on a diagram. [An agentic workflow is not an automation](https://lenvanderhof.com/en/blog/agentic-workflow-vs-automation/). A script that calls a model is still a script. An **AI agent** takes a goal, chooses tools, and keeps going. That is the useful definition for operators. It is also the dangerous one. An agent that can mail, spend, or open a pull request is not “AI.” It is a junior hire with no employment contract. Walk one object through the three boxes. “Summarise this PDF in the chat” is a chatbot. “When a PDF lands in this folder, extract the invoice total into the sheet” is automation. “Chase unpaid invoices this week, using the sheet and the mail tool, and stop if a customer disputes” is an agent, but only if someone wrote the stop. The [glossary capsule](https://lenvanderhof.com/glossary/ai-agent/) is the short form. This page is the test you run in a meeting. ## The charter is the definition I do not call a system an agent until it has a written charter. Seven fields, the same ones I use for human operators in [CHORUS](https://lenvanderhof.com/frameworks/chorus/): - purpose - inputs - outputs - authority ceiling - success criteria - review requirement - escalation If you cannot fill those fields, you do not have an agent. You have a demo. Demos are allowed. Demos do not get the production key. Filled, for the invoice worker: - **Purpose.** Collect overdue invoices this week without starting a legal fight. - **Inputs.** The receivables sheet dated today. The last approved reminder template. - **Outputs.** A send-ready draft per overdue row, or a skip with a reason. - **Authority ceiling.** Draft only. No send. No new discount. No promise of legal action. - **Success criteria.** Every draft names the invoice number and the true amount. A skip is valid if the row is disputed. - **Review.** Founder fails any draft that invents a fee or changes due date. - **Escalation.** Anything that looks like a dispute goes to the founder before a second draft. That is seven fields. Not six (that is a handoff packet). Not four (that is a slogan). The [CHORUS](https://lenvanderhof.com/frameworks/chorus/) Charter line is the same list for a human or an agent. The human in the loop is not a person glancing at a dashboard. It is a [named reviewer](https://lenvanderhof.com/glossary/human-in-the-loop/) who can fail the output against the success criteria. No named reviewer, no loop. The [override doctrine](https://lenvanderhof.com/glossary/override-doctrine/) is the other half of the charter. The charter says what the agent does. The doctrine says what it must refuse: spending above a ceiling, speaking as the company, changing production data, closing a judgment you still own. [MCP](https://lenvanderhof.com/en/blog/mcp-explained-for-founders/) is how that worker is allowed to touch the building: visibility, mutation, log. It is not the definition of the worker. A clean server with no charter is still a hole with nicer plumbing. ## Where this sits in the library [SENSE](https://lenvanderhof.com/frameworks/sense/) decides **where** an agent belongs in a founder’s week: which signal is worth a standing system, which claim needs a confidence grade, which Monday decision changes. The [90-day calendar](https://lenvanderhof.com/en/blog/sense-90-day-intelligence-layer/) is Diagnose, Deploy, Evaluate. [AI Agents for Startup Strategy](https://lenvanderhof.com/ai-agents-for-startup-strategy/) is the book that installs that layer. [Why multi-agent systems fail](https://lenvanderhof.com/en/blog/why-multi-agent-systems-fail/) is what happens when you add three of these workers and skip the protocol. Capability is cheap. Coordination is not. [STACK](https://lenvanderhof.com/frameworks/stack/) is the next door. Once you have a real agent, the repo it lives in starts to rot unless the agent OS is versioned like the app. That is a different article. This page does not sell a runtime. Runtimes change names. The three tests and the charter do not. ## A five-minute audit Pick one system you already call an agent. 1. Write the goal in one sentence that still makes sense tomorrow. 2. List the tools it can touch. If “whatever the plugin list is” is the answer, you do not have a list. 3. Name the human who can stop a call. A role is not a name. 4. Write the one action it is forbidden to take. 5. Write the last time that human actually failed an output. If any line is blank, stop using the word agent for that system until the line is filled. The vocabulary is the control. Loose vocabulary is how a chatbot inherits an API key. ## Terminology - [AI agent](https://lenvanderhof.com/glossary/ai-agent/) - [Human in the loop](https://lenvanderhof.com/glossary/human-in-the-loop/) - [SENSE](https://lenvanderhof.com/glossary/sense/) - [Override doctrine](https://lenvanderhof.com/glossary/override-doctrine/) ## Sources 1. [AI agent (glossary)](https://lenvanderhof.com/glossary/ai-agent/) 2. [SENSE framework](https://lenvanderhof.com/frameworks/sense/) 3. [AI Agents for Startup Strategy](https://lenvanderhof.com/ai-agents-for-startup-strategy/) ## Related essays - [MCP explained for founders](https://lenvanderhof.com/en/blog/mcp-explained-for-founders/) - [AI Agents for Startup Strategy: introduction](https://lenvanderhof.com/en/blog/ai-agents-for-startup-strategy-introduction/) - [The Agentic Codebase: introduction](https://lenvanderhof.com/en/blog/the-agentic-codebase-introduction/) - [The Multi-Agent Organization: introduction](https://lenvanderhof.com/en/blog/the-multi-agent-organization-introduction/) - [Why multi-agent systems fail](https://lenvanderhof.com/en/blog/why-multi-agent-systems-fail/) - [A SENSE intelligence layer in 90 days](https://lenvanderhof.com/en/blog/sense-90-day-intelligence-layer/) - [Version the agent OS](https://lenvanderhof.com/en/blog/stack-version-the-agent-os/) - [An agentic workflow is not an automation](https://lenvanderhof.com/en/blog/agentic-workflow-vs-automation/) - [LLM integration is an operating-design problem](https://lenvanderhof.com/en/blog/llm-integration-is-operating-design/) - [A go-to-market system that survives the first ten customers](https://lenvanderhof.com/en/blog/gtm-that-survives-ten-customers/) - [AI agent or chatbot: three tests before you mix the words](https://lenvanderhof.com/en/blog/ai-agent-or-chatbot/) - [MCP meaning: Model Context Protocol, not a product](https://lenvanderhof.com/en/blog/mcp-meaning/) - [What is STACK? Five layers, not a vendor diagram](https://lenvanderhof.com/en/blog/what-is-stack/) - [What is CHORUS? Coordination, not a choir](https://lenvanderhof.com/en/blog/what-is-chorus/) ## Further reading - [AI agent (glossary)](https://lenvanderhof.com/glossary/ai-agent/) - [SENSE](https://lenvanderhof.com/frameworks/sense/) - [AI Agents for Startup Strategy](https://lenvanderhof.com/ai-agents-for-startup-strategy/) - [MCP explained for founders](https://lenvanderhof.com/en/blog/mcp-explained-for-founders/) - [Why multi-agent systems fail](https://lenvanderhof.com/en/blog/why-multi-agent-systems-fail/) - [An agentic workflow is not an automation](https://lenvanderhof.com/en/blog/agentic-workflow-vs-automation/) - [STACK](https://lenvanderhof.com/frameworks/stack/) About the author ## [Len P. van der Hof](https://lenvanderhof.com/en/authors/len-p-van-der-hof/) Entrepreneur, AI Innovator and Venture Builder Len P. van der Hof builds practical AI systems, digital ventures and evidence-informed tools for founders. ```json { "@context": "https://schema.org", "@graph": [ { "@type": "Person", "@id": "https://lenvanderhof.com/#person", "name": "Len P. van der Hof", "alternateName": [ "Len van der Hof", "L.P. van der Hof", "Leendert Pieter van der Hof" ], "honorificSuffix": "MSc", "url": "https://lenvanderhof.com/", "image": [ "https://lenvanderhof.com/photos/len-portrait-1.jpg", "https://lenvanderhof.com/photos/len-portrait-2.jpg", "https://lenvanderhof.com/photos/len-portrait-3.jpg", "https://lenvanderhof.com/photos/len-portrait-4.jpg", "https://lenvanderhof.com/photos/len-speaking.jpg", "https://lenvanderhof.com/photos/len-hero.jpg" ], "jobTitle": "Entrepreneur, AI Innovator and Venture Builder", "description": "Len P. van der Hof is a Dutch entrepreneur and AI innovator building ReasonKit, MindSesh, Undominated.ai, the fiction imprint LPH98.lifestyle, and technology ventures through LPH98.ventures.", "address": { "@type": "PostalAddress", "addressLocality": "Zwijndrecht", "addressCountry": "NL" }, "alumniOf": { "@type": "CollegeOrUniversity", "name": "Rotterdam School of Management, Erasmus University" }, "knowsAbout": [ "Artificial intelligence", "AI agents", "Agentic AI systems", "LLM routing", "SEO", "Generative engine optimization", "Answer engine optimization", "Venture building", "Founder performance", "Founder psychology", "Evidence-based decision-making" ], "sameAs": [ "https://www.linkedin.com/in/lenvanderhof/", "https://x.com/LenvanderHof", "https://www.youtube.com/channel/UCTG20buKqYYbitqqf7l3zJA", "https://www.instagram.com/Lenvanderhof/", "https://www.threads.com/@lenvanderhof", "https://github.com/Lenvanderhof", "https://huggingface.co/LPH98", "https://www.npmjs.com/~lenvanderhof", "https://www.goodreads.com/author/show/70983905.Len_P_van_der_Hof", "https://www.amazon.com/author/lenvanderhof", "https://www.bol.com/nl/nl/b/len-p-van-der-hof-msc/609879394/", "https://bsky.app/profile/lenvanderhof.com", "https://mastodon.social/@Lenvanderhof", "https://crates.io/users/Lenvanderhof", "https://cursor.com/@Lenvanderhof", "https://medium.com/@Lenvanderhof", "https://gitlab.com/Lenvanderhof", "https://hub.docker.com/u/lenvanderhof/", "https://dev.to/lenvanderhof", "https://www.facebook.com/Lenvanderhof", "https://soundcloud.com/Lenvanderhof" ], "affiliation": [ { "@id": "https://lenvanderhof.com/#publisher" }, { "@id": "https://lenvanderhof.com/#mindsesh" }, { "@id": "https://lenvanderhof.com/#lifestyle" } ] }, { "@type": "WebSite", "@id": "https://lenvanderhof.com/#website", "url": "https://lenvanderhof.com/", "name": "Len P. van der Hof", "description": "Len P. van der Hof is a Dutch entrepreneur and AI innovator building ReasonKit, MindSesh, Undominated.ai, the fiction imprint LPH98.lifestyle, and technology ventures through LPH98.ventures.", "inLanguage": [ "en", "nl" ], "publisher": { "@id": "https://lenvanderhof.com/#person" } }, { "@type": "Organization", "@id": "https://lenvanderhof.com/#publisher", "name": "LPH98.ventures", "url": "https://lph98.ventures", "founder": { "@id": "https://lenvanderhof.com/#person" } }, { "@type": "Organization", "@id": "https://lenvanderhof.com/#mindsesh", "name": "MindSesh", "url": "https://mindsesh.net", "founder": { "@id": "https://lenvanderhof.com/#person" } }, { "@type": "SoftwareApplication", "@id": "https://lenvanderhof.com/#reasonkit", "name": "ReasonKit", "url": "https://reasonkit.sh", "creator": { "@id": "https://lenvanderhof.com/#person" } }, { "@type": "SoftwareApplication", "@id": "https://lenvanderhof.com/#undominated", "name": "Undominated.ai", "url": "https://undominated.ai", "creator": { "@id": "https://lenvanderhof.com/#person" } }, { "@type": "Organization", "@id": "https://lenvanderhof.com/#lifestyle", "name": "LPH98.lifestyle", "url": "https://lph98.lifestyle", "founder": { "@id": "https://lenvanderhof.com/#person" } }, { "@type": "ImageObject", "@id": "https://lenvanderhof.com/en/blog/what-is-an-ai-agent/#primaryimage", "url": "https://lenvanderhof.com/media/generated/blog-hero-ai-agent-en-v2.d33563a274c3.wide.webp", "contentUrl": "https://lenvanderhof.com/media/generated/blog-hero-ai-agent-en-v2.d33563a274c3.wide.webp", "representativeOfPage": true }, { "@type": "BreadcrumbList", "@id": "https://lenvanderhof.com/en/blog/what-is-an-ai-agent/#breadcrumb", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://lenvanderhof.com/" }, { "@type": "ListItem", "position": 2, "name": "Blog", "item": "https://lenvanderhof.com/en/blog/" }, { "@type": "ListItem", "position": 3, "name": "AI Systems", "item": "https://lenvanderhof.com/en/blog/category/ai-systems/" }, { "@type": "ListItem", "position": 4, "name": "What is an AI agent? A definition founders can use", "item": "https://lenvanderhof.com/en/blog/what-is-an-ai-agent/" } ] }, { "@type": "WebPage", "@id": "https://lenvanderhof.com/en/blog/what-is-an-ai-agent/#webpage", "url": "https://lenvanderhof.com/en/blog/what-is-an-ai-agent/", "name": "What is an AI agent? A definition founders can use", "description": "An AI agent takes a goal, uses tools, and acts across steps. A chatbot answers a turn. An automation runs a script. Founders need a charter and a review gate before they call anything an agent.", "isPartOf": { "@id": "https://lenvanderhof.com/#website" }, "primaryImageOfPage": { "@id": "https://lenvanderhof.com/en/blog/what-is-an-ai-agent/#primaryimage" }, "breadcrumb": { "@id": "https://lenvanderhof.com/en/blog/what-is-an-ai-agent/#breadcrumb" }, "inLanguage": "en-GB" }, { "@type": "BlogPosting", "@id": "https://lenvanderhof.com/en/blog/what-is-an-ai-agent/#article", "mainEntityOfPage": { "@id": "https://lenvanderhof.com/en/blog/what-is-an-ai-agent/#webpage" }, "headline": "What is an AI agent? A definition founders can use", "description": "An AI agent takes a goal, uses tools, and acts across steps. A chatbot answers a turn. An automation runs a script. Founders need a charter and a review gate before they call anything an agent.", "datePublished": "2026-08-15T20:50:00.000Z", "author": { "@id": "https://lenvanderhof.com/#person" }, "publisher": { "@id": "https://lenvanderhof.com/#person" }, "image": [ "https://lenvanderhof.com/media/generated/blog-hero-ai-agent-en-v2.d33563a274c3.square.webp", "https://lenvanderhof.com/media/generated/blog-hero-ai-agent-en-v2.d33563a274c3.landscape.webp", "https://lenvanderhof.com/media/generated/blog-hero-ai-agent-en-v2.d33563a274c3.wide.webp" ], "articleSection": "AI Systems", "inLanguage": "en-GB" } ] } ```