--- type: Article name: "How much does an agent need to know before it can buy?" id: "https://selfe.ai/insights/known-and-matched/how-much-does-an-agent-need-to-know" url: "https://selfe.ai/insights/known-and-matched/how-much-does-an-agent-need-to-know" publisher: "did:web:selfe.ai" description: "Not everything. An AI agent working through a booking request doesn't need a business's full history, it needs the small number of facts that resolve the specific thing the person asked for. A page with forty things to say and none of them the right one loses to a page with three." datePublished: "2026-09-15T11:56:07.125Z" author: The Selfe team --- # How much does an agent need to know before it can buy? > Not everything. An AI agent working through a booking request doesn't need a business's full history, it needs the small number of facts that resolve the specific thing the person asked for. A page with forty things to say and none of them the right one loses to a page with three. ## In short - An agent matching a request checks a short list of decisive facts, not everything a business has ever written about itself. - The facts that matter are the ones that gate the actual decision: constraints, limits, specifics, not brand story. - The same pattern holds outside cottages: a fitness note on a walking tour does the same job as a pet policy on a cottage. - More content isn't more findable past the point where it buries the decisive fact under prose written for a browsing human. - Selfe's structured record of a business captures the facts that resolve real decisions, verified rather than volunteered. A well-documented business and a well-matched one aren't the same thing. The second is smaller, sharper, and far more useful to an agent trying to confirm a fit fast. ## Matching is fit-testing Two cottages near Buxton take dogs. One page opens with three paragraphs on the building's Georgian history before it mentions pets at all. The other says, plainly, near the top: two dogs, any size, boot room with a hose for muddy walks back from the Peaks. A family booking a walking weekend with a pair of spaniels doesn't need the Georgian history to decide. They need the second page's three facts, and they need them where an agent can find them without inferring anything. An agent working through a booking request isn't searching for everything a business has ever said about itself. It's checking a short list of facts against a specific ask: these dates, this party, this constraint. "Known" means the facts that gate the decision are present, current, and findable, not that everything about a business has been written down somewhere. ## The muddy-boots test Take the two-dog cottage again. The decisive facts aren't romantic ones: how many dogs, any size limit, is there somewhere to deal with wet, muddy kit before it goes in the car. Get those three right and an agent can confirm the match in one pass. Leave them implied, "dog-friendly" with no detail, and the agent either has to ask a follow-up question the family didn't want to answer, or passes on the property rather than risk recommending a mismatch. The same pattern holds for a very different kind of booking. A walking-tour operator listing a trip as "suitable for most fitness levels" tells an agent nothing about whether it's a sensible match for someone recovering from a knee injury. A specific note, up to ninety minutes, one steep section, an alternative flatter loop available, resolves the actual question in one line, where the vaguer phrase would have needed a follow-up call to settle. ## Past a point, more content buries the decisive fact The instinct runs the other way. A business assumes the fix for being overlooked is writing more, another paragraph, another gallery, another section of the site. Past a point, that's the opposite of useful: the decisive fact gets buried under prose that reads well to a person scrolling and does nothing for an agent checking a specific constraint. Volume isn't the same job as precision, and an agent rewards precision because that's what lets it commit to a recommendation rather than hedge one. ## Where this shows up for a business Selfe's structured record of a business isn't built as a content form asking it to describe itself exhaustively. It captures the specific facts that resolve real decision points, verified against the business's own systems rather than taken as marketing copy at face value, the same distinction "Being found is not the same as being bought from" makes at the level of the whole idea. A business with three checkable facts in the right place beats one with forty unchecked ones, every time an agent is deciding rather than just browsing. ## Does a longer "about us" page help an agent match us better? Not on its own. What helps is whether the specific facts a request depends on are present and checkable, however long or short the page is. ## How do we know which facts actually matter? They're the ones a real booking request would hinge on: a hard limit, a specific date-sensitive detail, anything that would otherwise need a follow-up question to confirm. ## 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.