--- type: WebPage name: The right job finds the right tool. id: "https://selfe.ai/agentic-commerce/resource-discovery" url: "https://selfe.ai/agentic-commerce/resource-discovery" publisher: "did:web:selfe.ai" description: "How Selfe publishes your capabilities, terms and address so AI agents can discover and call your business before they know its name." --- # The right job finds the right tool. > How Selfe publishes your capabilities, terms and address so AI agents can discover and call your business before they know its name. Your Selfe is published as a capability, not a web page. Agents can discover what it does, the terms it works under and where to call it before they know your name. ## The work comes before the name. An agent starts with a task, not a shortlist. It needs something that can supply a size by Friday, take a table for four or cover two nights and a dog. A capability register returns candidates, plus what each may be asked to do and its address. Selfe publishes that record for your business and keeps it current. This is infrastructure, not placement. It makes you discoverable before an agent can compare, verify or buy. ## What the record says. The capability record an agent reads before deciding whether to call. **What it can do.** The jobs your Selfe can perform, described in the language AI agents search. **What to send it.** The information a request must include before your Selfe can act. **Your terms.** What you will and will not accept, stated before anything is committed. **Where to call.** The address to call and proof that the Selfe answering is yours. **Always current.** Stock, availability and terms stay aligned with your booking or commerce systems. **Honister Slate Mine** A Keswick attraction, now readable by an agent in real time, through Visit Keswick. **Viridian Gallery** A Keswick art gallery, connecting through its own WooCommerce shop, via Visit Keswick. ## One record. Any agent that speaks the standard. Your record follows an open specification, not a private deal with one assistant or directory. Any compatible agent can read it, and you can publish it elsewhere if you leave Selfe. Selfe keeps it aligned as products, availability and terms change. You gain reach without maintaining a separate record for every channel. ## Worth reading next The latest on how AI agents actually work, written as it happens. **The request behind your booking button is what matters.** 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?** A dog-friendly stay in October sounds like a simple filter until an AI agent tries to act on it. What happens next depends on details a first-pass search never asks for. **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. ## Can an agent find us without already knowing our name? Yes. Agents discover capabilities by the job they need done, not only by business name. Your Selfe publishes what it can do, the terms and where to call, so an agent can qualify it before choosing a supplier. **Do we need to build our own AI agent?** No. Your Selfe is the business-side agent: it publishes your identity, permitted actions and terms. You set its boundaries; Selfe maintains the protocols. **What is an outside agent allowed to access?** Only the facts and actions your Selfe publishes for that purpose. Your playbook controls what may be answered, quoted, held, booked or paid without asking you. The systems behind Selfe are not handed over to an outside agent, and a request beyond the permitted action is refused or escalated. **What if all of this looks different in a year?** The assistants and protocols will change. Your underlying record should not need rebuilding every time they do. Selfe keeps the Echo separate from any one channel and maintains the connections around it, so a new surface can read the same business instead of starting the work again. **What stops something hammering our systems?** Requests reach Selfe through Cloudflare and are checked before anything is allowed near a booking or commerce system. Rate limits, identity checks and action permissions separate ordinary discovery from something attempting to transact. Your operational systems see only the requests that pass those controls. ## 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.