Skip to main content
When an agent says “the user approved”, that is the agent’s word. When your own system logs an approval, that is your word. Either may be true. But after an agent is tricked, or when a customer disputes a change, neither one shows that the account holder said yes. BotShield takes the yes from the account holder directly: on their own phone, in the BotShield app, with their passkey. Then it signs the record. It is the one record in the exchange that neither the party asking nor the agent acting could have written. BotShield never asks your customer for an ID, a document or a selfie. Your customer is already your customer, and their passkey is what answers. BotShield doesn’t decide anything either. It is not the checkout, the wallet or the card, and whether the change happens is your call.

Why it has to be independent

BotShield is separate from your company and from the agent, so the signed record stands on its own.
  • Outside the agent’s reach. The answer is given on the account holder’s own device, in a separate app, and requires user verification on the device that holds the passkey. An agent operating a browser or a signed-in session cannot give it.
  • Not the party asking. The signed result comes from someone other than the company that wanted the change. It is a record you did not write yourself, which is what makes it worth keeping.
  • Bound to the account holder. The request reaches the person whose account is BotShield Verified with you, on the device that holds their passkey.
  • Added to what you have. Your sign-in, your fraud checks and any approvals your agent platform offers all stay. BotShield adds an independent yes on top, from the account holder.
  • The same everywhere. Your customer sets up once. The same passkey answers at every company, and you do not build or run an approval system of your own.
The standards work points the same way. The Personal Agent Protocol’s roadmap sets the goal that a company can verify the user approved the exact terms “instead of trusting the Personal Agent’s word”, and lists “a third party attests to the approval” among the routes. That is what BotShield does. See the protocol’s roadmap.

What BotShield records

For an approval, BotShield signs a result that carries your request’s ID, what was approved, and when. A Proof of Resolution, from Agents Ask, also carries a pairwise ID for your agent and the account holder, and a hash of the confirmation the passkey signed. A decline and an expired request are recorded and reported, and are not signed. It carries no name, email address, document or phone number, because none was ever asked for. See The privacy boundary for the field-by-field list.

What a signed approval shows

It shows that the holder of the account’s passkey approved these exact terms, on their own device, at that time. Keep the signed result with your own record of the change.

Where you meet it