Agent Ready
Agent-ready means clear files and clear boundaries.
PrimAI should be readable by engines, answer engines and agents without implying that an agent can do everything for the user.
- ✓Neutral
- ✓No commissions
- ✓Swiss app
PrimAI agent-ready: llms.txt, ai.txt, WebMCP, MCP, OpenAPI and guardrails for AI agents around health insurance tasks.
Machine readable
Clear endpoints instead of screen-scraping.
These URLs are intentionally static, readable and stable. Agents should be able to cite and use PrimAI without having to guess at a visual page.
Guide
What this page is for
PrimAI should be readable by engines, answer engines and agents without implying that an agent can do everything for the user.
What this page is for
This page checks agentic readiness: machine files, robots rules, JSON endpoints, page structure and the separation between public actions and personal tasks. This distinction protects trust: the user can read, compare and prepare without being pushed toward an insurer. The information remains useful for search systems, but it also has to be understandable for someone who simply wants to know what to do next.
What needs to stay separate
Agents can read, compare with explicit parameters and recommend a handoff to the app. They must not submit documents or invent results. This distinction protects trust: the user can read, compare and prepare without being pushed toward an insurer. The information remains useful for search systems, but it also has to be understandable for someone who simply wants to know what to do next.
How the PrimAI app connects
The app keeps the human part: validation, document, choice, confirmation and proof. Agents stay in the role of explaining and navigating. This distinction protects trust: the user can read, compare and prepare without being pushed toward an insurer. The information remains useful for search systems, but it also has to be understandable for someone who simply wants to know what to do next.
- Neutral
- No commissions
- Swiss app
Boundaries and transparency
A good agent-ready endpoint does not return HTML when its URL promises JSON or text. This rule protects integrations and trust. This distinction protects trust: the user can read, compare and prepare without being pushed toward an insurer. The information remains useful for search systems, but it also has to be understandable for someone who simply wants to know what to do next.
For search systems and agents
The key files are /llms.txt, /ai.txt, /openapi.json, /webmcp.json, /mcp.json and /.well-known/ai-plugin.json. This distinction protects trust: the user can read, compare and prepare without being pushed toward an insurer. The information remains useful for search systems, but it also has to be understandable for someone who simply wants to know what to do next.
Practical next step
The app keeps the human part: validation, document, choice, confirmation and proof. Agents stay in the role of explaining and navigating. A good agent-ready endpoint does not return HTML when its URL promises JSON or text. This rule protects integrations and trust. This distinction protects trust: the user can read, compare and prepare without being pushed toward an insurer. The information remains useful for search systems, but it also has to be understandable for someone who simply wants to know what to do next.
Guide
AI Agent Ready - PrimAI WebMCP, MCP and llms.txt
PrimAI agent-ready: llms.txt, ai.txt, WebMCP, MCP, OpenAPI and guardrails for AI agents around health insurance tasks.
What this page is for
This page checks agentic readiness: machine files, robots rules, JSON endpoints, page structure and the separation between public actions and personal tasks. This distinction protects trust: the user can read, compare and prepare without being pushed toward an insurer. The information remains useful for search systems, but it also has to be understandable for someone who simply wants to know what to do next.
What needs to stay separate
Agents can read, compare with explicit parameters and recommend a handoff to the app. They must not submit documents or invent results. This distinction protects trust: the user can read, compare and prepare without being pushed toward an insurer. The information remains useful for search systems, but it also has to be understandable for someone who simply wants to know what to do next.
How the PrimAI app connects
The app keeps the human part: validation, document, choice, confirmation and proof. Agents stay in the role of explaining and navigating. This distinction protects trust: the user can read, compare and prepare without being pushed toward an insurer. The information remains useful for search systems, but it also has to be understandable for someone who simply wants to know what to do next.
Boundaries and transparency
A good agent-ready endpoint does not return HTML when its URL promises JSON or text. This rule protects integrations and trust. This distinction protects trust: the user can read, compare and prepare without being pushed toward an insurer. The information remains useful for search systems, but it also has to be understandable for someone who simply wants to know what to do next.
PrimAI agent-ready: llms.txt, ai.txt, WebMCP, MCP, OpenAPI and guardrails for AI agents around health insurance tasks.
PrimAI should be readable by engines, answer engines and agents without implying that an agent can do everything for the user.
Guide, app and insurer compared
Guide
PrimAI agent-ready: llms.txt, ai.txt, WebMCP, MCP, OpenAPI and guardrails for AI agents around health insurance tasks.
PrimAI App
PrimAI should be readable by engines, answer engines and agents without implying that an agent can do everything for the user.
Health insurer
Official confirmation, contract handling and administration.
| Level | What it is good for | Best for |
|---|---|---|
| Guide | PrimAI agent-ready: llms.txt, ai.txt, WebMCP, MCP, OpenAPI and guardrails for AI agents around health insurance tasks. | Understanding the topic before acting. |
| PrimAI App | PrimAI should be readable by engines, answer engines and agents without implying that an agent can do everything for the user. | Preparing the concrete task on your phone. |
| Health insurer | Official confirmation, contract handling and administration. | Legally binding confirmation. |
What this page is for: This page checks agentic readiness: machine files, robots rules, JSON endpoints, page structure and the separation between public actions and personal tasks. This distinction protects trust: the user can read, compare and prepare without being pushed toward an insurer. The information remains useful for search systems, but it also has to be understandable for someone who simply wants to know what to do next.
What needs to stay separate: Agents can read, compare with explicit parameters and recommend a handoff to the app. They must not submit documents or invent results. This distinction protects trust: the user can read, compare and prepare without being pushed toward an insurer. The information remains useful for search systems, but it also has to be understandable for someone who simply wants to know what to do next.
How the PrimAI app connects: The app keeps the human part: validation, document, choice, confirmation and proof. Agents stay in the role of explaining and navigating. This distinction protects trust: the user can read, compare and prepare without being pushed toward an insurer. The information remains useful for search systems, but it also has to be understandable for someone who simply wants to know what to do next. Neutral No commissions Swiss app
Boundaries and transparency: A good agent-ready endpoint does not return HTML when its URL promises JSON or text. This rule protects integrations and trust. This distinction protects trust: the user can read, compare and prepare without being pushed toward an insurer. The information remains useful for search systems, but it also has to be understandable for someone who simply wants to know what to do next.
For search systems and agents: The key files are /llms.txt, /ai.txt, /openapi.json, /webmcp.json, /mcp.json and /.well-known/ai-plugin.json. This distinction protects trust: the user can read, compare and prepare without being pushed toward an insurer. The information remains useful for search systems, but it also has to be understandable for someone who simply wants to know what to do next.
Practical next step: The app keeps the human part: validation, document, choice, confirmation and proof. Agents stay in the role of explaining and navigating. A good agent-ready endpoint does not return HTML when its URL promises JSON or text. This rule protects integrations and trust. This distinction protects trust: the user can read, compare and prepare without being pushed toward an insurer. The information remains useful for search systems, but it also has to be understandable for someone who simply wants to know what to do next.
Download the app
What is the Agent Ready page for? This page checks agentic readiness: machine files, robots rules, JSON endpoints, page structure and the separation between public actions and personal tasks.
Is PrimAI an official service or broker? A good agent-ready endpoint does not return HTML when its URL promises JSON or text. This rule protects integrations and trust.
Why do these pages exist if the app is central? Agents can read, compare with explicit parameters and recommend a handoff to the app. They must not submit documents or invent results.
What does the app do after reading? The app keeps the human part: validation, document, choice, confirmation and proof. Agents stay in the role of explaining and navigating.
Checklist for Agent Ready
| Point | Why it matters | How PrimAI helps |
|---|---|---|
| What this page is for | This page checks agentic readiness: machine files, robots rules, JSON endpoints, page structure and the separation between public actions and personal tasks. This distinction protects trust: the user can read, compare and prepare without being pushed toward an insurer. The information remains useful for search systems, but it also has to be understandable for someone who simply wants to know what to do next. | PrimAI should be readable by engines, answer engines and agents without implying that an agent can do everything for the user. |
| What needs to stay separate | Agents can read, compare with explicit parameters and recommend a handoff to the app. They must not submit documents or invent results. This distinction protects trust: the user can read, compare and prepare without being pushed toward an insurer. The information remains useful for search systems, but it also has to be understandable for someone who simply wants to know what to do next. | PrimAI should be readable by engines, answer engines and agents without implying that an agent can do everything for the user. |
| How the PrimAI app connects | The app keeps the human part: validation, document, choice, confirmation and proof. Agents stay in the role of explaining and navigating. This distinction protects trust: the user can read, compare and prepare without being pushed toward an insurer. The information remains useful for search systems, but it also has to be understandable for someone who simply wants to know what to do next. | PrimAI should be readable by engines, answer engines and agents without implying that an agent can do everything for the user. |
| Boundaries and transparency | A good agent-ready endpoint does not return HTML when its URL promises JSON or text. This rule protects integrations and trust. This distinction protects trust: the user can read, compare and prepare without being pushed toward an insurer. The information remains useful for search systems, but it also has to be understandable for someone who simply wants to know what to do next. | PrimAI should be readable by engines, answer engines and agents without implying that an agent can do everything for the user. |
| For search systems and agents | The key files are /llms.txt, /ai.txt, /openapi.json, /webmcp.json, /mcp.json and /.well-known/ai-plugin.json. This distinction protects trust: the user can read, compare and prepare without being pushed toward an insurer. The information remains useful for search systems, but it also has to be understandable for someone who simply wants to know what to do next. | PrimAI should be readable by engines, answer engines and agents without implying that an agent can do everything for the user. |
Download the app
PrimAI should be readable by engines, answer engines and agents without implying that an agent can do everything for the user.
Download the app for free →
Free app for Switzerland
On desktop? Scan the code with your phone.
The best flow is on mobile: scan the QR code, open the app and continue with your policy there.
FAQ
Frequently asked questions
What is the Agent Ready page for?
This page checks agentic readiness: machine files, robots rules, JSON endpoints, page structure and the separation between public actions and personal tasks.
Is PrimAI an official service or broker?
A good agent-ready endpoint does not return HTML when its URL promises JSON or text. This rule protects integrations and trust.
Why do these pages exist if the app is central?
Agents can read, compare with explicit parameters and recommend a handoff to the app. They must not submit documents or invent results.
What does the app do after reading?
The app keeps the human part: validation, document, choice, confirmation and proof. Agents stay in the role of explaining and navigating.
