In short
- The website must describe services, audiences and regions unambiguously.
- Sources and contact paths should be publicly verifiable.
- Agent functions need clear names, rules and internal recipients.
1. Content clarity
First check whether a person understands in less than a minute what your business offers, who it's for and which region it serves.
If this information sits only in images, sliders or generic claims, it's often too weak for AI systems.
2. Sources and evidence
For each important service there should be a stable public source. That can be a service page, documentation, contact page, calculator page or API description.
Sources help AI systems distinguish verified facts from marketing claims.
3. Contact and functions
A profile becomes AI-agent-ready only when an agent can not just read but also recognize an allowed action.
Typical functions are request a rate, request a quote, request a meeting, request a callback or ask a question. Each function should be routed internally to the right person.
Checklist
- Describe the main service in one clear sentence
- Make region, language and audience visible
- Link service and contact pages publicly
- Provide agent.md and agent.json
- Define at least one allowed agent function
- Set internal recipients per function
- Run a dry-run test via Agent API or MCP
Frequently asked
Does a business need its own API?
No. To start, email-based functions through agentready.ch are often enough. Your own API matters only when calculators, bookings or process data should be connected directly.
How fast can a base profile be created?
A profile can be prepared from public sources. A verified profile additionally needs a personal review and clear contact rules.
Ask Google AI
Ask ChatGPT
Ask Claude