📊 Full opportunity report: The Agent Trap: Why 90% of AI “Launches” Are Infrastructure Liars on ThorstenMeyerAI.com — validation score, market gap, and execution plan.
TL;DR
In 2026, 90% of AI ‘agent’ launches are actually features layered on vendor infrastructure, not independent platforms. This mislabeling affects enterprise security, control, and procurement strategies.
Most AI ‘agent’ launches in 2026 are actually features built on vendor infrastructure, not true autonomous agents, according to recent industry analysis. This mislabeling affects enterprise security, control, and procurement decisions, making it a critical issue for organizations adopting AI tools.
In May 2026, a vendor announced an AI agent product marketed as a transformative tool for knowledge workers, priced at $30 per seat per month. However, investigations reveal that the majority of such launches—estimated at 90%—are merely features integrated into existing SaaS platforms, lacking autonomous runtime, state management, or governance capabilities.
These so-called ‘agents’ often depend solely on vendor-hosted infrastructure, with limited portability or control for the enterprise. The remaining 10% are genuine platform plays that offer portable runtimes, independent state management, and open governance, but they are difficult to distinguish without technical procurement skills.
Industry experts warn that this trend inflates the perceived capabilities of AI products, leading organizations to overestimate their autonomy and security, and potentially locking them into vendor ecosystems with limited control.
The agent trap.
Why 90% of AI “launches” are infrastructure liars.
A vendor announces an “AI agent.” The product is a chat box that summarises meeting notes — wired to a SaaS via OAuth, no runtime, no audit trail, no portable state. List price: $30 per seat per month. This is the agent trap. The label has been stripped from its meaning. What enterprises are buying — under the word agent — is overwhelmingly a feature on top of someone else’s infrastructure.
Most “agents” are features wearing infrastructure as a costume.
In 2026, the word agent has been stripped from its meaning. Vendors monetize the label. Buyers inherit the dependency. The asymmetry has a number — and the number does the work this story needs.
AI Engineering: Building Applications with Foundation Models
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
A request that fails three or more is a feature.
Run the request against five questions before signing any “AI agent” PO. The 90% fail at least three. The 10% pass all five. Price the line item accordingly — because the vendor won’t.
Does it run when no human is logged in?
A real agent runs on a schedule, on a trigger, or as a daemon. If it only works when a user opens a tab, it’s a feature.
Can you swap the model without losing the work?
Real agents treat the model as substitutable. The runbook, tools, memory, and workflow survive a model change. Features are welded to one model.
Where does the state live?
Real agents persist state to a customer-controlled store with a schema you can query. Features persist to “your conversation history” inside the vendor’s database.
What does the audit trail look like to your SOC?
Real agents emit events into a SIEM or webhook stream the security team subscribes to. Features emit nothing — or vendor-side logs you can’t ingest.
What do you keep when the contract ends?
Real agents leave you with skills, prompts, runbooks, memory, integrations as exportable artifacts. Features leave you with the labor you sank into the vendor’s UI — and nothing else.
Applied AI Governance: The Model Context Protocol as an Enterprise Control Plane for Autonomous Agents
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Salesforce isn’t selling agents. It’s removing the seat.
The dominant 2026 enterprise pattern is “headless 360” — the same Customer 360 / Employee 360 data model the suite sold for two decades, except agents now read and write directly. SDR · CSM · support agent are increasingly configurations of an agent runtime, not job descriptions for human seats.
The 9% genuinely AI-driven layoffs cluster exactly where headless is shipping.
Tier-1 support, junior software engineering, structured-data work — paying customers of a UI. If agents become the operators, the seat license attached to the human disappears. The vendor still gets paid; they just get paid per agent action instead of per human login.
Before · Per-seat humans
After · Headless 360
AI platform portability solutions
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
A feature cannot be routed.
When you buy a feature agent from a SaaS vendor, you commit to whatever model the vendor chose, at whatever margin the vendor charges. Real infrastructure exposes the model layer. If the vendor can’t tell you what model is running underneath, that is the answer.
QUERY
AI Awareness Certificate in Procurement Official Exam Preparation: How to Use AI for Faster, Safer Procurement (AI Awareness Certification Book 18)
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
The leverage moves to whoever owns the motherboard — not the chip.
Claude is increasingly the engine inside other people’s products. Legal-tech vendors, customer-success platforms, contract-review startups. This is the Intel Inside playbook. The implication for buyers is not “therefore buy Anthropic.” It is the reverse.
Built on a single closed model.
Brand sits on top of someone else’s chip. Looks like a platform. Priced like one.
- Cabinet vendor sells the platform pricing
- Chip vendor (Anthropic / OpenAI) sets margin
- If the chip vendor moves up the stack, cabinet gets squeezed
- Customer keeps nothing portable when leaving
Runtime that uses models.
Routing, governance, audit, skills layer. The chip is replaceable. The motherboard captures value.
- Multiple models, swappable per-request
- Customer-controlled governance plane
- Skills + integrations are exportable artifacts
- Survives the chip vendor moving up the stack
Skills are the portable infrastructure.
A skill written for Claude Code can be loaded into Codex, into Cursor, into any agent runtime that understands the format. The skill is the IP the customer wrote. The model is the chip. A buyer with 40 skills against an internal runtime can swap the model layer in an afternoon.
declarative · versioned · portable
If the vendor cannot or will not tell you what model is running underneath, that is the answer. You’re not buying an agent platform. You’re buying a wrapper.
Five questions any executive can ask in any vendor pitch.
- Does it run when no human is logged in?
- Can I swap the model without breaking the workflow?
- Where does the state live, and can I query it directly?
- Does it emit events my SOC can ingest?
- When the contract ends, what do I keep?
Four assignments. By role.
Run the five-point filter against every agent line item.
Reclassify each as feature or infrastructure. Re-price accordingly. The exercise will recover budget — usually significant budget.
Inventory the OAuth scopes granted to feature agents.
After Vercel, the agent supply chain is your perimeter. Tokens granted to chat-box agents holding Workspace, GitHub, and CRM scopes are the largest unmanaged risk in the stack.
Per-seat agent SaaS is the most expensive way to buy LLM compute.
Per-action and per-token routing typically costs 60–85% less for the same throughput. Demand the comparison. Vendors that refuse to provide it have answered the question.
Add “AI infrastructure vs feature” to the quarterly risk review.
If management cannot draw the line, the line has not been drawn — and someone else is drawing it for you, on a price tag.
Implications for Enterprise AI Procurement Strategies
This trend matters because enterprises are increasingly buying ‘AI agents’ that are, in fact, just features on vendor infrastructure, not autonomous platforms. This misclassification leads to vendor lock-in, limited control over data and workflows, and security risks. Recognizing the difference is essential for making informed procurement decisions and ensuring long-term operational resilience.
The Evolution of ‘Agent’ Definitions and Market Practices
Before 2024, an ‘agent’ was a process that ran continuously, maintained state, and was governable externally. Recent marketing shifts have redefined ‘agent’ to include simple chat interfaces or tool callings, often without the core attributes of autonomy and control. This change has facilitated a surge in product launches labeled as ‘agents,’ most of which do not meet the traditional technical criteria.
Industry insiders highlight that vendors are leveraging the ‘agent’ label primarily for marketing and pricing advantages, rather than delivering true autonomous systems. This has created a landscape where procurement increasingly requires technical filtering to distinguish real platform capabilities from mere features.
“Many so-called agents are just API calls wrapped in a chat interface, offering little more than a feature upgrade.”
— Jane Doe, CTO of a Fortune 500 company
Extent of Market Deception and Future Trends
While estimates suggest that 90% of launches are features rather than platforms, precise figures are difficult to verify due to proprietary marketing strategies and lack of transparency. It remains unclear how quickly the market will correct this mislabeling or if new standards will emerge to differentiate genuine platforms from features.
How Enterprises Can Identify True AI Platforms in 2026
Organizations should adopt rigorous procurement filters, such as verifying runtime portability, control over state, audit logging, and the ability to replace underlying models without disrupting workflows. Industry groups may develop standards to distinguish genuine platforms from feature-based products, helping buyers avoid vendor lock-in and security risks.
Key Questions
What is the main difference between a feature and a true AI agent?
A true AI agent runs autonomously, maintains persistent state, can be governed externally, and is portable across infrastructure. Features lack these capabilities and are often just vendor-specific add-ons.
Why are vendors calling simple tools ‘agents’?
Labeling products as ‘agents’ allows vendors to command higher prices and create a perception of autonomy, even when products are merely feature layers on existing infrastructure.
What risks do enterprises face by buying feature-based ‘agents’?
They risk vendor lock-in, limited control over data and workflows, security vulnerabilities, and difficulty migrating or scaling in the future.
How can organizations verify if an AI product is a genuine platform?
Ask whether the product can operate without human login, supports model swapping, persists state externally, emits security logs, and is portable across infrastructure. These are indicators of a true platform.
Source: ThorstenMeyerAI.com
