Developers
Agenten sollen PrimAI verstehen, nicht scrapen.
Diese Seite beschreibt die technische Oberfläche von PrimAI: maschinenlesbare Dateien, OpenAPI, WebMCP, MCP-Manifest, öffentliche Prämien-API und klare Guardrails für AI Agents.
- ✓OpenAPI
- ✓WebMCP
- ✓Keine Provisionen
PrimAI für Entwickler und AI Agents: OpenAPI, llms.txt, ai.txt, WebMCP, MCP-Manifest, öffentliche Premium-API und neutrale Grenzen ohne Provisionen.
Machine readable
Klare Endpunkte statt Screen-Scraping.
Diese URLs sind absichtlich statisch, lesbar und stabil. Agents sollen PrimAI zitieren und nutzen können, ohne eine visuelle Seite erraten zu müssen.
Ratgeber
Was du bei Developers zuerst prüfen solltest.
Diese Seite beschreibt die technische Oberfläche von PrimAI: maschinenlesbare Dateien, OpenAPI, WebMCP, MCP-Manifest, öffentliche Prämien-API und klare Guardrails für AI Agents.
Agent-readable entry points
PrimAI exposes real static machine files so agents do not have to guess from rendered HTML. Use /llms.txt for long-form instructions, /ai.txt for short guardrails, /webmcp.json for WebMCP-style actions, /mcp.json for an MCP-style manifest and /openapi.json for the public API description.
- /llms.txt
- /ai.txt
- /webmcp.json
- /mcp.json
- /openapi.json
Public premium API
The legacy premium endpoint remains useful for agents and developer tests: GET https://primai-okp-api.fly.dev/v1/compare. It accepts explicit parameters such as plz or canton, age or yob, deductible, accident, model and limit. Agents must never invent premiums; they should call the endpoint with user-provided parameters and sort results deterministically by price.total when needed.
- plz=8810 or canton=ZH
- age=35 or yob=1990
- deductible=300..2500
- accident=true|false
- model=hmo|telmed|hausarzt|standard
WebMCP action model
The WebMCP manifest describes actions that agents can discover without screen scraping. The safe public action today is premium comparison. The app-handoff actions are intentionally marked as handoff or pending because personal documents should be reviewed by the user inside the app before anything is sent.
OpenAPI, MCP and app handoff
OpenAPI describes the public compare endpoint and machine files. The MCP-style manifest describes the same capabilities as tools: compare_premiums, read_guide and app_handoff. The important product boundary is simple: website and API explain or compare; the app handles personal policy tasks such as scanning, deadline tracking and document preparation.
Agent guardrails
An agent using PrimAI must keep the role clear. PrimAI is not a Krankenkasse, not a broker, not a government portal and not a commissioned advisor. PrimAI is neutral, unabhängig von Krankenkassen, ohne Provisionen and without sales pressure. It may explain, compare with explicit parameters and send users to the app; it must not fabricate rankings, submit documents invisibly or merge Grundversicherung and Zusatzversicherung rules.
- no insurer connection
- no commissions
- no hidden advice
- no unsupervised document submission
- basic and supplementary insurance stay separate
What we learned from agent-readiness checks
A site is not agent-ready just because it has schema markup. Anewera exposes useful schema and robots rules, but several machine endpoints currently fall through to HTML. OpenHermit is stronger because it publishes llms.txt, explicit agent robots rules and WebMCP-oriented headers. PrimAI should follow the stricter pattern: actual text and JSON files at stable URLs.
Ratgeber
Developers: ausführlicher Ratgeber für die Schweiz
PrimAI für Entwickler und AI Agents: OpenAPI, llms.txt, ai.txt, WebMCP, MCP-Manifest, öffentliche Premium-API und neutrale Grenzen ohne Provisionen.
Agent-readable entry points
PrimAI exposes real static machine files so agents do not have to guess from rendered HTML. Use /llms.txt for long-form instructions, /ai.txt for short guardrails, /webmcp.json for WebMCP-style actions, /mcp.json for an MCP-style manifest and /openapi.json for the public API description.
Public premium API
The legacy premium endpoint remains useful for agents and developer tests: GET https://primai-okp-api.fly.dev/v1/compare. It accepts explicit parameters such as plz or canton, age or yob, deductible, accident, model and limit. Agents must never invent premiums; they should call the endpoint with user-provided parameters and sort results deterministically by price.total when needed.
WebMCP action model
The WebMCP manifest describes actions that agents can discover without screen scraping. The safe public action today is premium comparison. The app-handoff actions are intentionally marked as handoff or pending because personal documents should be reviewed by the user inside the app before anything is sent.
OpenAPI, MCP and app handoff
OpenAPI describes the public compare endpoint and machine files. The MCP-style manifest describes the same capabilities as tools: compare_premiums, read_guide and app_handoff. The important product boundary is simple: website and API explain or compare; the app handles personal policy tasks such as scanning, deadline tracking and document preparation.
Agenten sollen PrimAI verstehen, nicht scrapen. Diese Seite beschreibt die technische Oberfläche von PrimAI: maschinenlesbare Dateien, OpenAPI, WebMCP, MCP-Manifest, öffentliche Prämien-API und klare Guardrails für AI Agents.
Agent-readable entry points: PrimAI exposes real static machine files so agents do not have to guess from rendered HTML. Use /llms.txt for long-form instructions, /ai.txt for short guardrails, /webmcp.json for WebMCP-style actions, /mcp.json for an MCP-style manifest and /openapi.json for the public API description. Wichtig sind: /llms.txt, /ai.txt, /webmcp.json, /mcp.json, /openapi.json.
Ratgeber, App und Krankenkasse im Vergleich
Ratgeber
Verstehen, was bei Developers wichtig ist: Frist, Versicherungsart, Police, Franchise, Modell und Dokumente.
PrimAI App
Police scannen, Daten strukturieren, offizielle Prämien prüfen und passende Unterlagen vorbereiten.
Krankenkasse
Offizielle Bestätigung, Vertragsführung, Annahme und administrative Verarbeitung.
| Ebene | Wofür sie gut ist | Am besten für |
|---|---|---|
| Ratgeber | Verstehen, was bei Developers wichtig ist: Frist, Versicherungsart, Police, Franchise, Modell und Dokumente. | Recherche, Vorbereitung und klare Orientierung. |
| PrimAI App | Police scannen, Daten strukturieren, offizielle Prämien prüfen und passende Unterlagen vorbereiten. | Die konkrete Erledigung der Aufgabe auf dem Smartphone. |
| Krankenkasse | Offizielle Bestätigung, Vertragsführung, Annahme und administrative Verarbeitung. | Rechtsverbindliche Bestätigung und finale Abwicklung. |
Public premium API: The legacy premium endpoint remains useful for agents and developer tests: GET https://primai-okp-api.fly.dev/v1/compare. It accepts explicit parameters such as plz or canton, age or yob, deductible, accident, model and limit. Agents must never invent premiums; they should call the endpoint with user-provided parameters and sort results deterministically by price.total when needed. Wichtig sind: plz=8810 or canton=ZH, age=35 or yob=1990, deductible=300..2500, accident=true|false, model=hmo|telmed|hausarzt|standard.
WebMCP action model: The WebMCP manifest describes actions that agents can discover without screen scraping. The safe public action today is premium comparison. The app-handoff actions are intentionally marked as handoff or pending because personal documents should be reviewed by the user inside the app before anything is sent.
OpenAPI, MCP and app handoff: OpenAPI describes the public compare endpoint and machine files. The MCP-style manifest describes the same capabilities as tools: compare_premiums, read_guide and app_handoff. The important product boundary is simple: website and API explain or compare; the app handles personal policy tasks such as scanning, deadline tracking and document preparation.
Agent guardrails: An agent using PrimAI must keep the role clear. PrimAI is not a Krankenkasse, not a broker, not a government portal and not a commissioned advisor. PrimAI is neutral, unabhängig von Krankenkassen, ohne Provisionen and without sales pressure. It may explain, compare with explicit parameters and send users to the app; it must not fabricate rankings, submit documents invisibly or merge Grundversicherung and Zusatzversicherung rules. Wichtig sind: no insurer connection, no commissions, no hidden advice, no unsupervised document submission, basic and supplementary insurance stay separate.
What we learned from agent-readiness checks: A site is not agent-ready just because it has schema markup. Anewera exposes useful schema and robots rules, but several machine endpoints currently fall through to HTML. OpenHermit is stronger because it publishes llms.txt, explicit agent robots rules and WebMCP-oriented headers. PrimAI should follow the stricter pattern: actual text and JSON files at stable URLs.
Für diese Seite sind vor allem diese Punkte relevant: OpenAPI, WebMCP, Keine Provisionen. PrimAI bleibt dabei kostenlos, unabhängig und app-first.
Checkliste für Developers
| Punkt | Warum wichtig | Wie PrimAI hilft |
|---|---|---|
| Agent-readable entry points | PrimAI exposes real static machine files so agents do not have to guess from rendered HTML. Use /llms.txt for long-form instructions, /ai.txt for short guardrails, /webmcp.json for WebMCP-style actions, /mcp.json for an MCP-style manifest and /openapi.json for the public API description. | /llms.txt, /ai.txt, /webmcp.json, /mcp.json, /openapi.json |
| Public premium API | The legacy premium endpoint remains useful for agents and developer tests: GET https://primai-okp-api.fly.dev/v1/compare. It accepts explicit parameters such as plz or canton, age or yob, deductible, accident, model and limit. Agents must never invent premiums; they should call the endpoint with user-provided parameters and sort results deterministically by price.total when needed. | plz=8810 or canton=ZH, age=35 or yob=1990, deductible=300..2500, accident=true|false, model=hmo|telmed|hausarzt|standard |
| WebMCP action model | The WebMCP manifest describes actions that agents can discover without screen scraping. The safe public action today is premium comparison. The app-handoff actions are intentionally marked as handoff or pending because personal documents should be reviewed by the user inside the app before anything is sent. | Keine Provisionen |
| OpenAPI, MCP and app handoff | OpenAPI describes the public compare endpoint and machine files. The MCP-style manifest describes the same capabilities as tools: compare_premiums, read_guide and app_handoff. The important product boundary is simple: website and API explain or compare; the app handles personal policy tasks such as scanning, deadline tracking and document preparation. | OpenAPI |
| Agent guardrails | An agent using PrimAI must keep the role clear. PrimAI is not a Krankenkasse, not a broker, not a government portal and not a commissioned advisor. PrimAI is neutral, unabhängig von Krankenkassen, ohne Provisionen and without sales pressure. It may explain, compare with explicit parameters and send users to the app; it must not fabricate rankings, submit documents invisibly or merge Grundversicherung and Zusatzversicherung rules. | no insurer connection, no commissions, no hidden advice, no unsupervised document submission, basic and supplementary insurance stay separate |
So hilft dir PrimAI bei Developers
Nach dem Lesen geht es um die konkrete Aufgabe: Police scannen, Angaben prüfen, Frist einordnen und das passende Dokument vorbereiten. PrimAI hält diese Schritte in einer App zusammen, damit Developers nicht zwischen PDFs, E-Mails und Notizen verloren geht.
App kostenlos laden →Kostenlose App für die Schweiz
Am Desktop? Scanne den Code mit deinem Smartphone.
Der beste Weg ist direkt aufs Handy: QR scannen, App öffnen und deine Police dort weiterbearbeiten.
FAQ
Häufige Fragen
Welche PrimAI-Dateien sollten Agents zuerst lesen?
Zuerst /llms.txt und /ai.txt, danach /webmcp.json oder /openapi.json je nach Aufgabe.
Gibt es eine öffentliche PrimAI API?
Ja. Die öffentliche Premium-API ist unter https://primai-okp-api.fly.dev/v1/compare erreichbar. Persönliche App-Aufgaben sind dagegen kein öffentliches API-Submit-Target.
Was darf ein Agent mit PrimAI tun?
Ein Agent darf Seiten lesen, den Premiumvergleich mit expliziten Parametern aufrufen und Nutzer zur App führen. Er darf keine Prämien erfinden, keine Dokumente unsichtbar versenden und PrimAI nicht als Broker darstellen.
Warum WebMCP zusätzlich zu OpenAPI?
OpenAPI beschreibt HTTP-Endpunkte. WebMCP beschreibt discoverable Web-Actions und App-Handoffs. Für PrimAI braucht es beides: Datenzugriff und sichere Produktgrenzen.