---
type: WebPage
name: Knowledge is sales.
id: "https://selfe.ai/insights"
url: "https://selfe.ai/insights"
publisher: "did:web:selfe.ai"
description: "What AI agents are actually doing, what the standards are doing, and what either means for somebody running a business."
---

# Knowledge is sales.

> What AI agents are actually doing, what the standards are doing, and what either means for somebody running a business.

What AI agents are actually doing, what the standards are doing, and what either means for somebody running a business rather than building one. Written when something happens, not to a schedule.

Selfe connects what you sell to the AI agents people increasingly use to choose and buy.

**Your booking button is not the point.** A booking button helps a person start a journey. An agent needs to establish the terms of a specific request, know what it may do and carry the relevant context into the next step.

**Someone asks for a dog-friendly stay in October. What happens next?** *(coming soon)* A real hospitality booking, walked through step by step, from the question an agent is actually asking to the reservation landing in your own system.

**How much does an agent need to know before it can buy?** *(coming soon)* A plain-English answer: sufficient facts, not exhaustive data. What actually has to be on record, and what doesn't.

**A table for four at eight is not a search query.** A customer request contains the variables that determine whether an offer is possible. Treating it as a loose search loses the information needed to give a trustworthy commercial answer.

**A product page is not the product.** *(coming soon)* Ecommerce edition: variants, stock, delivery and returns, and what an agent needs from each before it will commit to buying.

**The agent does not have a favourite.** *(coming soon)* Why accurate, current information beats brand familiarity the moment an agent is actually comparing options.

**What an AI agent checks before it trusts you.** *(coming soon)* Trust, translated into normal business terms: consistency, provenance, availability, payment. Nothing mystical about it.

**The digital work you already pay for still matters.** *(coming soon)* Where Selfe sits alongside your SEO, your agency, your catalogue and your booking system, not instead of any of them.

**Why 'available online' does not always mean available to buy.** A product page showing live stock is not the same as a product an AI agent can buy. The gap between the two is usually a missing action, not a missing fact.

**What happens when Google moves closer to the transaction?** Google increasingly lets someone research, compare and buy without ever leaving the search results page. An AI agent doing the same thing on someone's behalf needs the same thing Google's own tools do: real, current facts it can act on directly.

**The new shortlist.** *(coming soon)* What it actually takes to be considered when the customer has handed the choosing over to an agent.

**Three questions every business should ask about its AI readiness.** A useful readiness review asks whether an agent can find the business, establish what is true and make permitted commercial progress. It should end with the next fix, not a vague score.

**What we learned from testing real businesses in [area].** *(coming soon)* A regional field note, once we have permission to share it: the patterns that showed up when we tested real businesses on the ground.

**Agent-ready doesn't mean fully automated. Here's the difference.** Being ready for an AI agent to complete a purchase and letting every purchase complete without a person ever looking are two different decisions, and a business can choose the first without the second.

**Deposits, holds and cancellations: what an agent needs to know.** A hold, a deposit and a cancellation policy sound like one topic to a person booking a stay. An AI agent needs them treated as three separate, precisely stated facts, or it can misrepresent what's been committed.

**The three ways a transaction can still fail after the agent says yes.** An AI agent confirming a purchase isn't the end of the transaction. Three specific failure points sit between "yes" and the order completing, and each needs a different fix.

**Transactions for multi-unit operators: the same rules, every site.** A retailer running several shops shouldn't have to solve agent-ready transactions once per site. The rules an AI agent checks are one business decision, made once, not rewritten at every location.

**What happens when an agent's request doesn't match your rules.** A request that falls outside a business's rules doesn't have to end the transaction, as long as there's a real, bookable alternative behind it that an AI agent can complete.

**What has to be true before an agent presses confirm.** An AI agent completing a booking on someone's behalf needs more certainty than a person browsing does, because nobody is there to notice if something's wrong before it's confirmed.

**Agentic commerce for portfolios: one setup, every property.** A group running six cottages doesn't need to solve this problem six times. Getting one property right the hard way, and then repeating that work five more times, is usually the wrong approach entirely.

**The difference between a mention and a sale.** Most of what decides whether a recommendation becomes a booking happens after the mention, not during it. Here's what sits in that gap.

**What 'agentic commerce' means, in one paragraph.** The phrase gets used loosely enough that it's worth pinning down properly, once, rather than half-defining it on every other page that uses it.

**Why price alone doesn't win an agent's recommendation.** An AI comparing two nearly-identical products defaults to the one it can be most confident about. Price is only one part of that confidence, not the whole of it.

**Your customer's agent, not your customer: who's doing the shopping now.** A growing share of shopping isn't a person browsing a site at all. It's a standing agent, already trusted with the job, checking and buying on someone's behalf without them watching.

**How long it actually takes to go from unready to bookable.** The honest answer to "how long will this take" depends far less on how hard the technical work is than on how quickly a business can find the one fix an AI agent is genuinely waiting on.

**Readiness for portfolios: one score, many properties.** A business with several sites doesn't get several separate readiness problems. Most of what an AI agent finds wrong is usually the same gap, repeated, not a new one at each location.

**The one fix that moves the readiness needle fastest.** Most businesses try to fix everything a readiness check flags at once. The faster route is finding the single fix that's genuinely blocking an AI agent, and doing that one first.

**The readiness score, explained: what each number actually measures.** A readiness score isn't measuring whether an AI agent likes your business. It's measuring three separate, specific things, and knowing which one is low is worth more than the number itself.

**What a failed readiness check actually looks like.** A failed readiness check rarely looks dramatic. It usually looks like an AI agent quietly giving up or guessing, which is harder to notice than an obvious error.

**Why "we're on Google" isn't the same as being agent-ready.** Ranking well in a search engine and being ready for an AI agent to book you are answering two different questions, and a business can pass one completely while failing the other.

**Multi-brand retailers: keeping every label distinct when an agent is comparing.** *(coming soon)*

**Returns and sizing: the two questions agents ask that catalogues rarely answer.** *(coming soon)*

**Variants, stock and delivery: what an agent checks before it recommends.** *(coming soon)*

**What a product feed needs that a product page doesn't.** *(coming soon)*

**What makes one listing easier for an agent to sell than another.** *(coming soon)*

**Why "in stock" isn't the same as "buyable."** *(coming soon)*

**Where agentic commerce is actually heading, not the hype version.** *(coming soon)*

**The businesses that will be ready before anyone asks them to be.** *(coming soon)*

**The standards still being written, and why that's not a reason to wait.** *(coming soon)*

**The standing agent, not the search box: why less research happens on the open web at all.** *(coming soon)*

**What changes for discovery in the next twelve months.** *(coming soon)*

**What changes for transactions once agents hold payment credentials.** *(coming soon)*

**What happens to reviews once agents are the ones reading them.** *(coming soon)*

**Being found vs being bought from — what's the difference?** *(coming soon)*

**What is agentic commerce?** *(coming soon)*

**What counts as a verified fact?** *(coming soon)*

**What does "agent-ready" mean?** *(coming soon)*

**What is a buyability check?** *(coming soon)*

**What is a Curator?** *(coming soon)*

**What is a readiness score?** *(coming soon)*

**What is a Wallet, in the Selfe sense?** *(coming soon)*

**What is A2A?** *(coming soon)*

**What is an agent credential?** *(coming soon)*

**What is an AI agent?** *(coming soon)*

**What is an Echo?** *(coming soon)*

**What is AP2?** *(coming soon)*

**What is Folio?** *(coming soon)*

**What is Groundry?** *(coming soon)*

**What is MCP?** *(coming soon)*

**What is structured data, for AI?** *(coming soon)*

**What is UCP?** *(coming soon)*

**Activities and tours: what "suits who" actually means to an agent.** *(coming soon)*

**Cottages, hotels, and the difference agents don't care about.** *(coming soon)*

**Restaurants, pubs and the booking that isn't just a table.** *(coming soon)*

**Theatres and attractions: showtimes, casts and who a show is for.** *(coming soon)*

**What a room rate needs to say that a listing page doesn't.** *(coming soon)*

**How to check what AI is already saying about you.** Being found by an AI agent is the easy half of the job. Here's how to check where you stand today, and why the check itself only ever tells you half the story.

**Structured data, explained without the jargon.** A returns policy that says "just get in touch if there's a problem" and one that says "returns accepted within 30 days, unworn, tags attached" can describe the same shop. Only one of them can be checked by something that isn't a person using judgement.

**What changes the moment you go from mentioned to shortlisted.** Being mentioned by an AI agent and being one of the two or three options it puts in front of someone are different achievements, and the second one is decided by a narrower set of facts than the first.

**What it means for an AI to know a place, not just describe it.** A product description tells an AI agent what a shop says about itself. Being known is a different, higher bar: whether an AI can trust what it's told enough to act on it.

**What it means to be found by an agent that already knows the person asking.** A standing AI agent that already knows its person skips the broad question a search engine expects entirely. It arrives already narrowed, checking a shop's facts against one specific person's specific needs.

**Why two businesses with the same facts get different recommendations.** Two shops can publish exactly the same facts about a similar product and still get recommended unevenly. The difference is rarely the facts. It's how confidently an AI agent can act on them.

**One setup, every surface: what that actually requires.** A canal boat hire company doesn't need a separate connection for every AI agent that asks about its boats. One live source of truth, built once, is what lets it answer ChatGPT, Google and everything that comes after the same way.

**Personal agents and what changes when your customer's agent already knows them.** A ceramics studio investing in being found on every surface a shopper might browse has nothing to offer a customer whose personal AI agent already knows exactly what they want and isn't browsing anywhere at all.

**The surfaces where agents choose and buy.** Customers increasingly begin in places that help them research, compare and progress a purchase. The durable task is to make a business understandable and actionable across those surfaces without rebuilding everything for each one.

**The other kind of agent: when there's no chat window at all.** A walking-tour company checking its visibility in ChatGPT and Google is checking the wrong thing entirely for a growing share of its potential bookings, the ones arriving through an AI agent nobody ever sees typing a question.

**What a standard actually buys you over a one-off integration.** A one-off integration solves the surface one AI agent is asking from today. An open standard solves the shape of the question, which is what every future surface will keep asking in some form.

**What a standing agent checks that a one-off chat session never does.** A one-off chat session checks a business's facts once and moves on. A standing AI agent checks the same facts again next week, and the week after, which changes what "current" needs to mean.

**What changes when ChatGPT can check out directly.** Being mentioned favourably by an AI agent used to be the whole test. Once that same agent can complete a purchase without leaving the conversation, it needs a live, checkable answer, not just a good description.

**Why building for one AI platform is a losing bet.** A distillery that built its entire readiness around one AI agent's specific integration now has to rebuild every time a new one arrives. Facts connected to an open standard serve every surface, current and future, from one piece of work.

**"AI agents will replace your website." No, and here's what actually happens to it.** *(coming soon)*

**"AI can just read the page, you don't need structured data." We tested that claim. It doesn't hold up.** *(coming soon)*

**"Being mentioned by ChatGPT means you're winning." It doesn't, and treating it that way is costing you bookings.** *(coming soon)*

**"Bigger platforms will sort this out for us." Why we don't think that's coming, or coming for everyone.** *(coming soon)*

**"Just add a chatbot" was never a strategy. Here's the argument for why.** *(coming soon)*

**A lot of what you've heard about AI bookings isn't quite right.** *(coming soon)*

**"This is years away." We saw it happen to a business last month.** *(coming soon)*

**Your local knowledge is a sales asset.** The best local knowledge lives entirely in conversation, asked for and answered in person. That's exactly the knowledge an AI agent can't reach, however good the website is.

**The things an agent cannot guess.** Getting found and getting matched are two different jobs. A business can nail the first and still lose the second, because an AI agent only knows what it's been told, never what it could have worked out by being there.

**What 'agent-ready' means.** "Agent-ready" gets used to mean almost anything. Here's what it requires, in one chain, and where most businesses are further along than they think, and further behind than they hope.

**Can an agent buy from you?** Being chat-visible and being buyable are different tests. Most shops pass the first without ever finding out whether they'd pass the second.

**Being found is not the same as being bought from.** This is the distinction the rest of this hub, and most of this site, keeps coming back to. Being found by an AI is real progress. It is not, on its own, a booking, a sale, or a reason to stop.

**The first thing an agent gets wrong about your business.** An AI agent rarely gets a business wrong out of carelessness. It gets it wrong because the fact that would have changed the answer was never written down anywhere it could check.

**Nobody asked for you by name. You got the sale anyway.** The strongest position in agentic commerce isn't brand recognition. It's being genuinely, checkably right for the request, even when nobody's ever heard of you.

**A2A, explained: how one agent proves what it's asking another to do.** *(coming soon)*

**Agent credentials: the token that says "yes, actually let this agent buy."** *(coming soon)*

**AP2 and agent payments: how an agent proves it's allowed to spend on someone's behalf.** *(coming soon)*

**Holds, mandates and spend limits: how a business keeps control of an automated payment.** *(coming soon)*

**MCP, explained: what it actually connects, and what it doesn't.** *(coming soon)*

**The plumbing behind every agent purchase.** *(coming soon)*

**UCP and the checkout handoff: what changes when a purchase completes inside the conversation.** *(coming soon)*

**What a checkout API call looks like from the other side.** *(coming soon)*

**What makes information safe enough for an agent to act on?** An agent should not turn a confident sentence into a commercial promise. Information becomes actionable when its source, scope, timing and next permitted use are clear.

**Trust for DMOs: what it means to vouch for someone else's business.** *(coming soon)*

**What happens when your data disagrees with itself.** *(coming soon)*

**What "verified" actually means, source by source.** *(coming soon)*

**Why a five-star review isn't evidence an agent can use.** *(coming soon)*

## Act on this

- [Check whether an agent can buy from you](https://selfe.ai/agentic-commerce/buyability-check) — the free readiness scan.
- [Discover venues](https://selfe.ai/api/registry/discover) — `POST`, semantic browse across the registry.
- [Match a bookable answer](https://selfe.ai/api/registry/match) — `POST` with dates and party size.
- [Verify Selfe's identity](https://selfe.ai/.well-known/did.json) — `did:web:selfe.ai`.
- [Agent card](https://selfe.ai/.well-known/agent-card.json) — how to connect over A2A or MCP.