--- type: WebPage name: Do take our credentials for it. id: "https://selfe.ai/agentic-commerce/trust" url: "https://selfe.ai/agentic-commerce/trust" publisher: "did:web:selfe.ai" description: "How Selfe lets each side verify identity, delegated authority and evidence before an agent can commit a transaction." --- # Do take our credentials for it. > How Selfe lets each side verify identity, delegated authority and evidence before an agent can commit a transaction. Before an agent commits anyone, both sides can verify the identity, authority and evidence behind the request. Each resolves to a signed record, not an assertion. Selfe carries your credentials so an agent can check them itself, without a phone call. ## Strangers can still say yes. An agentic transaction asks for a decision at speed. There is real money, an unfamiliar caller and no person available to size it up. Selfe checks the caller, what it may agree and the evidence behind the offer before the request reaches your systems. A failed check is refused and recorded. You can accept a legitimate request without trusting a stranger on sight. ## The checks before a request can commit. **Verifiable credentials.** Ratings, licences and accreditations signed by their issuer. **Both identities.** The business, the caller and the customer it represents. **Delegated authority.** The scope the agent may agree before you commit. **A right of refusal.** A failed check stops the request and records why. **Sorted before it lands.** Cloudflare stops ordinary nuisance; the rest is classified before anything answers. **Ye Olde Friars** Keswick's own mint cake maker, connecting through its Shopify shop, via Visit Keswick. **Visit Keswick** The Keswick Tourism Association itself, curating its members into one agent-readable roster, the relationship every other real entry here goes live through. ## Credentials that travel with the deal. Selfe turns a rating, licence or accreditation into a signed record an agent can verify in the moment. Your existing certificate or scheme stays as it is. Its proof now travels with the offer, so a buyer can act without a phone call. ## Worth reading next The latest on how 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. ## What do the credentials actually prove? They show who issued a claim, who is making a request and what authority the agent carries. They make those things verifiable; they do not make an unsupported claim true. **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 does Selfe do when it is not sure?** It stops and asks, showing the conflict, sources and decision required. Everything it settles alone is logged. Your answer can become a playbook rule, so the same uncertainty does not keep returning. **Who owns what Selfe knows about us?** Your business data and the Echo built for your business remain available to you and can be exported. Facts taken from public or third-party sources remain attributable to those sources rather than becoming ours or yours by repetition. Nothing in the working record is hidden from you or held back if you leave. **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.