A growing share of your website’s visitors are not people. They are agents — shopping for their humans, researching for their humans, booking for their humans. The web is starting to renovate for them, and if you run a website, this renovation will reach you. Here is an honest map of it: what’s emerging, what it misses, and what you can do this week.

The wave

Three patterns are showing up across the agent-web conversation, and all three are worth taking seriously.

Answer endpoints. Instead of forcing an agent to scrape your marketing pages, you expose a question-answering surface — a documented endpoint where an agent asks in natural language and gets a grounded answer about your product, hours, or policies. Think of it as a front desk for machines.

Pages as MCP servers. The Model Context Protocol gives agents a standard way to discover a site’s tools and resources — not just “here is text” but “here are the actions and data this site offers, typed and named.” A page stops being only a document and starts being an interface.

Signed agent cards. Coordination standards in the A2A family propose machine-readable manifests — an agent card — describing who an agent or service is, what it can do, and how to verify it cryptographically. Identity and capability, declared instead of guessed.

These are good ideas. We name them positively on our own developers page, and myOrbit speaks these dialects too — this very site ships machine-readable metadata for crawlers and agents. The standards people are converging on real problems: discovery, capability description, verification.

What “agent-ready” misses

Now the uncomfortable part. You can implement all three patterns and still have a website that merely answers well.

A site that answers isn’t a site that acts. An answer endpoint is read-only by nature. When the agent’s human wants to book, buy, reschedule, or complain, an answering site hands back a link — and the human is back to filling in forms. The last mile got no shorter; it just got a better brochure.

The gaps are structural:

  • No memory. Each agent visit starts from zero. The customer who asked yesterday is a stranger today. Statelessness is what made the web scale; it is also what makes it incapable of relationships.
  • No authority. An endpoint can describe your refund policy. It cannot grant a refund, because nothing behind it is entitled to decide anything.
  • No accountability. When an answer is wrong, who is responsible? A stateless endpoint has no audit trail of commitments, so there is nothing to hold to account.

Agent-ready, in the current sense, means legible to agents. Legible is the floor. It is not the building.

What “agent-staffed” means

The step beyond legibility is representation: a persistent twin that acts as your site’s front-of-house.

Staffed means there is someone home — an entity with three properties an endpoint can’t have:

Memory. The twin remembers the visitor, the conversation last month, the order in flight. Two agents asking about the same customer’s issue get one coherent story, because there is one entity holding it.

Agency. Within the rules you set, it transacts — takes the booking, quotes the job, issues the credit. The visiting agent leaves with an outcome, not a link.

Governance. This is what makes agency safe to grant. The twin runs under the same audited governance as everything else on the platform — the pipeline the Echo OS page describes. A stateless endpoint can’t be governed because it holds no authority; a twin holds authority precisely because it is governed.

The difference in one line: an agent-ready site can tell a visiting agent your return policy. An agent-staffed site can accept the return.

What you can do today

You don’t need to wait for any of this to settle. Everything below is standard, vendor-neutral, and useful for human visitors too.

Structure your content. Semantic HTML and schema.org markup for products, events, FAQs, and organization data. Agents parse structure far more reliably than prose — and this is the same work that improves accessibility and search.

Stabilize your anchors and ids. Agents cite and deep-link. If your headings have no ids, or your ids change every deploy, every reference into your site rots. Treat heading ids and URLs as API surface: stable, meaningful, versioned with care.

Ship machine-readable metadata. An accurate sitemap. A robots policy that says which automated readers are welcome. A plain-text overview of what your site is and offers, at a well-known path, so an agent’s first fetch lands on signal instead of navigation chrome.

Expose real capabilities deliberately. If you have an API, describe it in a machine-discoverable way; MCP is a reasonable bet for making a site’s tools discoverable. Start read-only. Add write actions only where you can enforce limits — the governance question arrives the moment you let an agent do anything.

Keep your promises findable. Prices, policies, hours — in text, in one canonical place each. Agents are ruthless about inconsistency: two pages disagreeing about your refund window is how an agent’s summary quietly costs you a customer.

And one thing from us, labeled honestly: the myOrbit embed — your twin, staffing your own website — is coming, not live. Today a twin meets customers in the app and by QR; the embed is the same entity arriving at your domain. When it ships, the sites that did the list above will be the ones ready to staff.

The order of operations

The agent web is arriving in the order webs always arrive: first legible, then interactive, then inhabited. Answer endpoints and agent cards are the legible phase, and they are worth doing now.

Just don’t mistake the floor for the building. Agents are not coming to your website to read. They are coming to get things done for their humans — and the sites that win will be the ones where somebody is home.