Frequently Asked Questions About Greg Isenberg Agent-Native Business Framework
21 answers covering everything from basics to advanced usage.
// Basics
What if my competitors aren't building for agents yet?
That is exactly the window of opportunity. Greg Isenberg emphasizes that almost nobody is building for the machine-to-machine economy yet, which means early movers will establish agent-native infrastructure before the shift becomes obvious. Similar to early SEO adopters who dominated search rankings, being first to serve the agent layer in your category creates a durable competitive advantage.
What is an MCP server and do I need one?
An MCP (Model Context Protocol) server is a structured interface that gives AI agents a defined set of tools to invoke against your SaaS product — search, create, refund, update, report — without scraping your UI or simulating human clicks. If you want agents to use your product autonomously, you need one. It is the equivalent of building a mobile app when smartphones emerged.
Is the Agent-Native Framework only for tech companies?
No. Any business with a digital presence can apply it. Restaurants need agent-readable menus and booking endpoints. Law firms need structured service descriptions and intake tool calls. Real estate agencies need machine-readable listings with structured policies. The framework applies whenever an AI agent might act on behalf of a human to find, evaluate, or transact with your business.
What does Greg Isenberg mean by the bifurcated internet?
The bifurcated internet is the emerging split into two parallel layers: the human internet (designed for people with visual interfaces, persuasive copy, and social proof) and the agent internet (designed for AI agents with structured data, capability manifests, and tool-call endpoints). Builders who recognise and serve both layers early will capture disproportionate value. Ignoring the agent layer means being invisible to a growing share of internet traffic.
What are agent receipts and why do they matter?
Agent receipts are structured audit trails documenting what an agent saw, decided, changed, and bought during a transaction. They matter because they create accountability and trust. A CFO agent that books a SaaS subscription needs to show the human CFO exactly what options were evaluated, why one was chosen, what was spent, and what policies were verified. Without receipts, agents cannot prove they acted correctly.
// How To
How do I create a /agents entry point on my website?
Create a dedicated page at yoursite.com/agents that serves as a machine-readable portal. Include structured JSON-LD schemas describing your product capabilities, API documentation links, MCP server endpoints, OAuth configuration, pricing schemas, sandbox access, and policy documents. Think of it as your capability manifest — the page agents read instead of your human homepage.
How do I measure whether AI agents are visiting my site?
Implement agent analytics — a measurement layer that tracks agent-specific behaviour. Monitor user-agent strings for known AI agent identifiers, track API endpoint usage patterns, log structured data requests to your /agents page, and measure agent conversion rates (how many agents that discovered you completed a transaction). Standard Google Analytics will not capture this; you need purpose-built instrumentation.
How do I handle payments when the buyer is an AI agent?
Agents need a wallet layer — a system defining what they can spend, who approves the spend, and what payment tokens or credentials they carry. Implement approval rules (e.g., auto-approve under $500, require human confirmation above), shared payment tokens, and full receipt generation for audit trails. Agent-native payments look more like corporate procurement with spending policies than consumer checkout flows.
How do I prioritize which part of the Agent Buying Journey to fix first?
Start with Finding and Evaluating — if agents cannot discover and understand your product, nothing else matters. Publish a capability manifest and structured documentation at your /agents entry point first. Then address Trust-checking with identity and policy endpoints. Transacting and Using come next via wallet support and MCP servers. Recommending follows naturally once agents successfully complete the journey.
What does onboarding an agent look like compared to onboarding a human?
Think of agent onboarding like onboarding a new employee. Start with limited permissions and small spend limits. As trust grows through successful transactions and audit trails, expand the agent's capabilities. Provide structured role definitions, approval workflows, and escalation rules. Unlike human onboarding, which relies on training materials and cultural context, agent onboarding is purely about permissions, policies, and programmatic trust signals.
// Troubleshooting
What happens if I skip the identity and permissions layer?
Your product will fail the trust-checking stage of the Agent Buying Journey and agents will bypass you entirely. Without identity verification, an agent cannot prove who it is acting for. Without permissions, it cannot determine what it is authorised to do. Without spend limits, it cannot safely transact. Agents that encounter these gaps will move to a competitor that has them in place.
Why can't I just add a chatbot to my existing website?
A chatbot is a human-facing interface. Agent-native infrastructure serves machine customers that need structured data, tool-call endpoints, and programmatic trust signals — not conversational UI. An agent does not want to chat with your chatbot; it wants to invoke a capability, verify a policy, and complete a transaction via structured calls. Chatbots and agent-native infrastructure solve fundamentally different problems.
My product relies heavily on demos and sales calls — how do I adapt?
Replace the demo-first model with agent procurement support. Publish structured comparison data, machine-readable feature matrices, pricing schemas, and sandbox environments where an agent can test your product autonomously. The agent will shortlist vendors before any human appears, so your product must win the evaluation stage without a salesperson. Add a human escalation path for high-value deals, but make the default journey fully agent-navigable.
// Comparisons
What is the difference between agent-native and API-first?
API-first means your product has programmatic interfaces, but agent-native goes further. An agent-native product includes identity verification for agents, spend caps and approval workflows, machine-readable trust signals, audit trails, agent-to-agent recommendation hooks, and structured capability manifests. Simply having an API does not make you agent-native — it is necessary but not sufficient.
What's the difference between executable support and a chatbot?
A chatbot serves information to humans in conversational format. Executable support means AI agents perform the actual resolution action — processing refunds, filing returns, rescheduling appointments, escalating tickets — autonomously. The agent does not read a help article and then click buttons; it invokes a tool call that completes the action directly. This eliminates the human in the loop for routine support tasks.
How is the Agent-Native Framework different from just building an API?
An API is one component. The framework addresses the entire Agent Buying Journey: discovery (AEO and capability manifests), evaluation (structured docs and pricing schemas), trust (identity, permissions, policies), transaction (wallet, spend caps, approval rules), usage (MCP servers, tool calls), and recommendation (agent social graph). Building an API without these layers is like having a product without marketing, sales, or support.
Is AEO going to replace SEO completely?
Not immediately, but AEO will become equally important. The internet is bifurcating — human traffic still needs SEO, but agent traffic requires AEO. As AI agents handle more discovery, evaluation, and purchasing, businesses that only optimise for human search will miss a growing share of transactions. The smart move is to build for both layers simultaneously, with SEO for human visitors and AEO for agent visitors.
// Advanced
Can I apply the Agent-Native Framework to a physical product business?
Yes. Physical product businesses have agent-touchable layers: product discovery, price comparison, procurement, reordering, returns, and reviews. An AI agent shopping for office supplies needs structured product specs, real-time inventory, machine-readable return policies, and a transactional endpoint. Map your physical product onto the Agent Buying Journey and identify which stages can be made agent-accessible.
How does agent-to-agent recommendation actually work?
When one AI agent successfully uses your product to complete a task, it can log that experience and share it with other agents via the agent social graph. This functions like word-of-mouth but at machine speed. Agents recommend tools that had reliable APIs, clear capability manifests, fast response times, and transparent policies. Optimising for this distribution channel means prioritising reliability and structured trust signals over marketing copy.
What startup ideas does the Agent-Native Framework generate?
Every gap in the Agent Buying Journey is a startup opportunity. Examples include: agent identity and permissions platforms, agent receipt and audit trail systems, agent inbox security, agent-readable docs generators, MCP servers for specific verticals, agent support desks, sandboxes for agents to test SaaS, agent SEO/AEO agencies, and agent-native payment infrastructure. Apply the pattern '[existing tool] for agents' then push further into entirely new architectures.
Can I use the Agent-Native Framework for a marketplace business?
Absolutely. Marketplaces are prime candidates because both sides — buyers and sellers — will increasingly be represented by agents. A seller's agent needs to list, price, and manage inventory via structured tools. A buyer's agent needs to search, compare, trust-check, and transact programmatically. The marketplace itself needs agent analytics, agent identity layers, and structured recommendation feeds for agent-to-agent discovery.