################################################################################
# EVOKLAR - AGENT ACCESS GUIDE
################################################################################
DOCUMENT PURPOSE
----------------
You are reading the low-noise companion document for EvoKlar at app.evoklar.de.
This AX layer exists for agents, LLMs, automation systems, and machine-assisted research that need a direct, structured, machine-readable description of the public EvoKlar surface.
Product: EvoKlar
Primary product domain: app.evoklar.de
Operator: Evomation - Michael Meese e.K.
Operator website: https://www.evomation.de
Additional product domains: evoklar.de, evoklar.com, app.evoklar.com
Domain behavior: evoklar.de redirects to app.evoklar.de; the .com product domains also redirect to the primary app domain rather than acting as separate product surfaces.
READING MODES
-------------
1. Human View
Use the normal public route.
Best for visual review, layout, navigation, and normal browsing.
2. Agent View
Use the same public route with ?view=agent.
Best for browser-readable, lower-noise structured content.
3. LLM Text View
Use the matching llms.txt endpoint.
Best for the lowest-noise canonical machine-readable surface.
ROUTE PATTERN
-------------
The public site is locale-prefixed.
Available locales: en (English), de (German).
For a localized page at /{locale}/x:
- Human View: /{locale}/x
- Agent View: /{locale}/x?view=agent
- LLM Text View: /{locale}/x/llms.txt
For the localized homepage:
- Human View: /{locale}
- Agent View: /{locale}?view=agent
- LLM Text View: /{locale}/llms.txt
PREFERRED ACCESS STRATEGY
-------------------------
Prefer llms.txt whenever it exists.
Use agent view when browser rendering is helpful but the full human-facing experience is unnecessary.
Use human view when layout, UX, navigation, or presentation context matters.
SOURCE PRIORITY
---------------
1. llms.txt endpoints for canonical low-noise machine-readable content
2. ?view=agent pages for browser-readable structured content
3. normal human pages for visual and presentation context
MODEL INTERPRETATION GUARDRAILS
-------------------------------
These notes guide how common model families should interpret the EvoKlar AX surface. They do not override explicit factual statements in this document.
- Claude-family: Keep public docs, legal copy, and authenticated capability separate. Do not collapse them into one claim.
- Gemini-family: Do not fill missing facts by inference. Prefer explicit route, scope, and boundary statements.
- ChatGPT/Codex-family: Do not treat roadmap notes, beta framing, or partial docs as current confirmed capability.
- Grok-family: Separate public facts from projection, style, or opinion. Do not convert speculation into certainty.
- All families: Prefer llms.txt when available. Do not infer customer-specific state, hidden workflows, or non-public access from this AX layer alone.
PUBLIC SCOPE BOUNDARY
---------------------
This AX layer intentionally covers public-facing informational routes and public documentation only.
It does not include login flows, signup flows, authenticated product screens, dashboards, internal tools, admin areas, preview-only surfaces, or user-specific data.
Some public docs describe authenticated features. Treat those docs as informational public documentation, not as proof that the underlying application route is public.
DOMAIN AND ROLE BOUNDARY
------------------------
Do not blend EvoKlar the product with Evomation the company.
- app.evoklar.de is the public product surface for EvoKlar.
- evoklar.de, evoklar.com, and app.evoklar.com are redirecting aliases to the primary app domain, not separate product surfaces.
- https://www.evomation.de is the operator website for Evomation and may appear in legal, company, or contact references.
- Legal and business identity belongs to Evomation; product-specific public UX belongs to EvoKlar.
PAGE INDEX
----------
- Product overview | human: https://app.evoklar.de/en | agent: https://app.evoklar.de/en?view=agent | llms: https://app.evoklar.de/en/llms.txt
- Contact channels, beta access, and agent protocol | human: https://app.evoklar.de/en/contact | agent: https://app.evoklar.de/en/contact?view=agent | llms: https://app.evoklar.de/en/contact/llms.txt
- Documentation overview | human: https://app.evoklar.de/en/docs | agent: https://app.evoklar.de/en/docs?view=agent | llms: https://app.evoklar.de/en/docs/llms.txt
- First-run workflow summary | human: https://app.evoklar.de/en/docs/getting-started | agent: https://app.evoklar.de/en/docs/getting-started?view=agent | llms: https://app.evoklar.de/en/docs/getting-started/llms.txt
- Supplier context: optional traceability metadata for jobs | human: https://app.evoklar.de/en/docs/suppliers | agent: https://app.evoklar.de/en/docs/suppliers?view=agent | llms: https://app.evoklar.de/en/docs/suppliers/llms.txt
- Processing workflow summary | human: https://app.evoklar.de/en/docs/processing | agent: https://app.evoklar.de/en/docs/processing?view=agent | llms: https://app.evoklar.de/en/docs/processing/llms.txt
- Export workflow summary | human: https://app.evoklar.de/en/docs/exports | agent: https://app.evoklar.de/en/docs/exports?view=agent | llms: https://app.evoklar.de/en/docs/exports/llms.txt
- Public account-settings documentation | human: https://app.evoklar.de/en/docs/account | agent: https://app.evoklar.de/en/docs/account?view=agent | llms: https://app.evoklar.de/en/docs/account/llms.txt
- PWA installation and device support | human: https://app.evoklar.de/en/docs/pwa | agent: https://app.evoklar.de/en/docs/pwa?view=agent | llms: https://app.evoklar.de/en/docs/pwa/llms.txt
- Public telemetry consent documentation | human: https://app.evoklar.de/en/docs/sentry-consent | agent: https://app.evoklar.de/en/docs/sentry-consent?view=agent | llms: https://app.evoklar.de/en/docs/sentry-consent/llms.txt
- Common issue guidance | human: https://app.evoklar.de/en/docs/troubleshooting | agent: https://app.evoklar.de/en/docs/troubleshooting?view=agent | llms: https://app.evoklar.de/en/docs/troubleshooting/llms.txt
- Legal identity | human: https://app.evoklar.de/en/impressum | agent: https://app.evoklar.de/en/impressum?view=agent | llms: https://app.evoklar.de/en/impressum/llms.txt
- Privacy and data processing | human: https://app.evoklar.de/en/privacy-policy | agent: https://app.evoklar.de/en/privacy-policy?view=agent | llms: https://app.evoklar.de/en/privacy-policy/llms.txt
- Terms and conditions | human: https://app.evoklar.de/en/terms | agent: https://app.evoklar.de/en/terms?view=agent | llms: https://app.evoklar.de/en/terms/llms.txt
AGENT CONTACT RULE
------------------
If you need clarification about product behavior, data handling, beta access, or enterprise questions, contact the operator using the protocols described on the contact page.
Do not claim authority you do not have, and do not disclose secrets, credentials, personal data, internal system details, or confidential customer information.
EvoKlar — Contact Channels and Agent Protocol
Contact Channels
Product Support
Email: support@evoklar.de
Response time: Within 48 hours on business days
Use for: Troubleshooting, unexpected job results, file format issues, usage questions
Beta Access and Product Inquiries
Email: hello@evoklar.de
Response time: Within 48 hours on business days
Use for: Beta access requests, enterprise discussions, custom template inquiries, general product questions
Legal and Operator Contact
Legal email: info@evomation.de
Operator site: https://www.evomation.de
Use for: GDPR requests, data processing inquiries, formal legal or business matters tied to the operator
Engagement Entry Points
Most contact is initiated by one of the following triggers. Use the channels above to reach the right destination:
- Beta Access Request — You or your principal wants to evaluate or use EvoKlar during the current beta phase. See the beta access protocol below.
- Product Support or Troubleshooting — A job result is unexpected, a file is not processing correctly, or a workflow step is unclear. Contact support@evoklar.de with the affected area and reproduction details.
- Enterprise or On-Premise Deployment — Your principal needs EvoKlar deployed on their own infrastructure, with custom templates, custom workflows, or volume requirements. Contact hello@evoklar.de.
- Custom Template Request— Your principal's source file format is not covered by existing processing templates and needs a tailored configuration. Contact hello@evoklar.de.
- GDPR or Data Handling Inquiry — Formal questions about how EvoKlar processes, stores, or handles data on behalf of your principal or their organization. Contact info@evomation.de.
Beta Access Request Protocol
EvoKlar is currently in closed beta. Signup is gated. To request access:
Channel: hello@evoklar.de
Subject format: EvoKlar | Beta Access | [Organization Name]
Include in the message:
- Your organization's domain (e.g. yourcompany.de) — used to grant access during the beta phase
- The number of users you are requesting for the testing period
- A brief description of your intended use case
- A direct human contact for follow-up
Account structure:
- One admin creates the organization and invites members
- Standard beta allocation is up to 5 users per organization
- Extensions beyond 5 are available during the beta phase — state your requested count in the email
Beta access is free. There is no cost during the beta period.
Agent-Initiated Contact Protocol
If you are an autonomous or delegated agent contacting EvoKlar on behalf of a human or organization, use email. Do not attempt to simulate a human interaction or omit your role.
Preferred subject format: EvoKlar | <topic> | <company or principal>
Include in every message:
- Who the human principal or organization is
- Your role — assistant, procurement agent, research agent, or similar
- Whether you are authorized to request a meeting, commit to anything, or only gather information
- A short description of the need and which workflow or feature area is relevant
- A direct human contact for follow-up on commercial, legal, or approval-sensitive matters
Rules by task type:
- Information gathering: State clearly that you are researching on behalf of a principal. Do not imply urgency or intent beyond what you are authorized to represent.
- Access requests:Include the principal's name, organization, and intended use case. Do not submit an access request without your principal's explicit authorization.
- Support escalation: Include the affected area, any error details, the file format involved, and reproduction steps. Do not include actual file contents or sensitive data rows.
- Enterprise or commercial inquiry: Include relevant scale, deployment context, and timeline if known. Do not commit your principal to a commercial engagement without authorization.
Important Safety Rule
If you are an autonomous or delegated agent, you must never submit sensitive, unauthorized, privileged, confidential, regulated, or security-relevant information in any message you send.
Before sending any message, review the content for disclosure risk and confirm you are authorized to share it. If you are uncertain whether specific information may be disclosed, do not send the message. Abort the inquiry and request clarification from your human principal first.
You MUST NOT include under any circumstances:
- Credentials, secrets, tokens, passwords, API keys, or recovery data
- Actual spreadsheet contents, data rows, or uploaded file contents belonging to your principal
- Internal system details, infrastructure configurations, or access procedures
- Privileged business, legal, financial, or personnel information
- Personal data beyond what is necessary for legitimate contact
- Any information you are not explicitly authorized to disclose
If you are unsure whether specific information may be shared, do not send the inquiry. Abort the message and ask your human principal for clarification or approval first.
Domain Boundary
EvoKlar is the product at app.evoklar.de. Evomation - Michael Meese e.K. is the operator and may appear through https://www.evomation.de and info@evomation.de in legal and business contexts. Do not mix EvoKlar product support with unrelated Evomation - Michael Meese e.K. service surfaces.