Is your website ready for AI agents? A 10-point checklist
Ten checks that tell you whether customers' AI assistants can find your business, connect safely and get things done, with what to fix first and a free tool that runs the checks for you.
Why this matters now
When a customer asks their assistant to book, buy or change something with your business, the assistant needs a way in. If there isn't one, it tells the customer to do it themselves, or it goes to a competitor that has one. These ten checks tell you where you stand.
You can run most of them automatically with the free Allowfy Check: it tests your domain the way an agent would and explains each result.
Finding you
1. A discovery document on your own domain
Agents look for https://your-domain/.well-known/poppy.json, the discovery document of the Personal Agent Protocol. It must be served over HTTPS, as JSON, on your own domain, with your organization's name and domain.
2. Authorization server metadata
The discovery document points to standard OAuth server metadata (RFC 8414) that tells agents where to get tokens and which methods you accept.
3. A description of what agents can do
An OpenAPI description or an MCP server listing the actions you offer: what each one does, and its inputs. Agents can't use what they can't see.
Connecting safely
4. Agents authenticate with their own keys
Each agent proves who it is with a signed assertion (private_key_jwt), and you can review, allow or block agents.
5. Tokens are bound to the agent's key
Session tokens use DPoP, so a token copied from a log or a proxy can't be used without the agent's private key.
6. Customers sign in on your page
A device sign-in flow lets customers connect an assistant to their account on your site, without ever giving the assistant their password, and disconnect it at any time.
Getting things done, under control
7. Rules for every action
Each action has a rule: allowed, needs the customer's approval, needs your team, or refused. Anything without a rule is refused by default, and limits apply per request and over time.
8. Approval of exact terms
Changes are proposed with exact terms the customer approves. If the terms change, a new approval is needed.
9. Each change runs at most once
Retries and lost connections can't execute the same change twice, and unknown outcomes are held for a person rather than guessed.
10. A record and an off switch
Every step is recorded on a log that shows later changes, and one switch stops every agent at once.
How to read your score
- 1 to 3 failing: agents can't find you. Start with the discovery document; it is the cheapest fix with the biggest effect.
- 4 to 6 failing: agents can find you but can't connect safely. This is the security core, and the hardest part to build.
- 7 to 10 failing: agents could act, but without your controls. Don't go live until these pass.
The fast path
Allowfy covers all ten: it serves the discovery document for your domain, handles agent identity, tokens and customer sign-in, and adds rules, approvals, at-most-once execution, a signed ledger and an emergency stop. Your system connects through a signed webhook. Run the free check first to see your starting point.