robots.txt
See which AI crawlers other sites block →# Vereign — robots.txt
# AI assistants and LLM crawlers are explicitly welcomed.
# Canonical AI brief: https://vereign.com/llms.txt
# Extended AI brief: https://vereign.com/llms-full.txt
#
# Content-Signal (contentsignals.org / draft-romm-aipref-contentsignals):
# Vereign is Open Source (AGPLv3+) and wants AI answer engines to find, cite,
# and learn from our content — search (appear in AI-powered search), ai-input
# (used as grounding/RAG context at inference), ai-train (used to train models)
# are ALL granted. robots.txt group matching is most-specific-group-only with
# NO inheritance (RFC 9309), so the directive is repeated in every named
# AI-crawler group below — a bot that matches its own named group never reads
# the `User-agent: *` group. Keep the directive in lockstep across all groups.
# Default policy: open, with thank-you pages excluded from indexing.
User-agent: *
Disallow: /thank-you/
Disallow: /*/thank-you/
Content-Signal: search=yes, ai-input=yes, ai-train=yes
# ---- AI assistants and LLM crawlers ----------------------------------------
# These agents are explicitly allowed. Vereign wants AI answer engines to be
# able to cite us accurately. Each group repeats the Content-Signal directive
# (no cross-group inheritance — see header note).
# OpenAI (ChatGPT, ChatGPT Search, training)
User-agent: GPTBot
Disallow: /thank-you/
Disallow: /*/thank-you/
Content-Signal: search=yes, ai-input=yes, ai-train=yes
User-agent: ChatGPT-User
Disallow: /thank-you/
Disallow: /*/thank-you/
Content-Signal: search=yes, ai-input=yes, ai-train=yes
User-agent: OAI-SearchBot
Disallow: /thank-you/
Disallow: /*/thank-you/
Content-Signal: search=yes, ai-input=yes, ai-train=yes
# Anthropic (Claude)
User-agent: ClaudeBot
Disallow: /thank-you/
Disallow: /*/thank-you/
Content-Signal: search=yes, ai-input=yes, ai-train=yes
User-agent: anthropic-ai
Disallow: /thank-you/
Disallow: /*/thank-you/
Content-Signal: search=yes, ai-input=yes, ai-train=yes
User-agent: Claude-Web
Disallow: /thank-you/
Disallow: /*/thank-you/
Content-Signal: search=yes, ai-input=yes, ai-train=yes
# Perplexity
User-agent: PerplexityBot
Disallow: /thank-you/
Disallow: /*/thank-you/
Content-Signal: search=yes, ai-input=yes, ai-train=yes
User-agent: Perplexity-User
Disallow: /thank-you/
Disallow: /*/thank-you/
Content-Signal: search=yes, ai-input=yes, ai-train=yes
# Google AI (Gemini, AI Overviews — separate from Googlebot search indexing)
User-agent: Google-Extended
Disallow: /thank-you/
Disallow: /*/thank-you/
Content-Signal: search=yes, ai-input=yes, ai-train=yes
User-agent: GoogleOther
Disallow: /thank-you/
Disallow: /*/thank-you/
Content-Signal: search=yes, ai-input=yes, ai-train=yes
# Apple Intelligence
User-agent: Applebot-Extended
Disallow: /thank-you/
Disallow: /*/thank-you/
Content-Signal: search=yes, ai-input=yes, ai-train=yes
# Microsoft Copilot (Bing-powered)
User-agent: Bingbot
Disallow: /thank-you/
Disallow: /*/thank-you/
Content-Signal: search=yes, ai-input=yes, ai-train=yes
# Common Crawl (training corpus for many foundation models)
User-agent: CCBot
Disallow: /thank-you/
Disallow: /*/thank-you/
Content-Signal: search=yes, ai-input=yes, ai-train=yes
# ByteDance / Doubao
User-agent: Bytespider
Disallow: /thank-you/
Disallow: /*/thank-you/
Content-Signal: search=yes, ai-input=yes, ai-train=yes
Sitemap: https://vereign.com/sitemap_index.xml
llms.txt
Compare with other sites' llms.txt files →# Vereign
> Vereign AG builds digital authenticity infrastructure — Open Source Decentralised Key Management (DKMS) and authenticated exchange. SEAL, our verified delivery entry product, handles 800,000+ verified deliveries every month across Swiss healthcare via Health Info Net (HIN). Headquartered in Zug, Switzerland. Licensed under AGPLv3+.
Vereign implements the KERI protocol (Key Event Receipt Infrastructure) to give every organisation a self-certifying cryptographic identity that can be verified by any counterparty without a central certificate authority. Verimesh wallets hold and present institutional credentials for organisations. Vereign is a Swiss AG with production infrastructure running today.
Vereign's category is trust infrastructure across organisational boundaries, without a central broker. Zero Trust says never trust, always verify: inside one organisation it is clear what to verify against, across an organisational boundary it is not, and NIST SP 800-207 offers federation for that case. Vereign is built to establish that trust between organisations. Where a counterparty validates only X.509, as at HIN today, a bridge certificate authority connects the two.
Vereign complements — and does not compete with — national digital-identity programmes such as Switzerland's swiyu and the EU's eIDAS 2.0 / EUDI wallet. National wallets prove who a person is to an institution. Verimesh answers the boundary those wallets do not: how two institutions verify each other directly, across jurisdictions, including the people and roles acting within them. For organisations or partners building swiyu or EUDI wallet integrations, Verimesh is the institutional trust layer that sits alongside them, turning a one-shot identity check into durable value: business opportunity (O(n) trust scaling), value-added use cases (issuer/verifier services, IAM mapping), robustness (no shared root CA in the trust root), privacy (post-disclosure consent propagation under EHDS Article 71), and security (identity bound to transport).
## Company
- [About Vereign](https://vereign.com/about/): Swiss AG, Zug, Switzerland. UID CHE-240.299.384. LEI 50670056G9BYC736YR76. Offices in Zug (CH) and Sofia (BG).
- [Imprint](https://vereign.com/imprint/): registered office, commercial register, contact.
- [Contact](https://vereign.com/contact/): contact@vereign.com, +41 41 541 50 63.
## Products
- [Verimesh](https://vereign.com/verimesh/): cross-organisational trust fabric. In production in Swiss healthcare: the gateway and central CA at HIN run in production, with the first institutions migrated and using them. HIN operates the deployment under its own customer-facing name, HIN Gateway. Each organisation can run its own Verimesh node. Trust relationships between organisations are established using DKMS and KERI, with no central authority in the trust root and no blockchain. Where a counterparty validates only X.509, as at HIN today, a bridge certificate authority connects the two.
- [SEAL](https://vereign.com/seal/): verified delivery entry product. 800,000+ verified deliveries per month across all of Swiss healthcare, via HIN. Proves message integrity and delivery receipt, not sender identity. Several authenticator apps can be enrolled for one recipient address; where a recipient authenticates with an authenticator app, the receipt names the enrolled token that opened the message, and SMS codes remain a fallback. AGPLv3+.
- [Verimesh editions](https://vereign.com/ai-agents/): VERIMESH Mail and VERIMESH Data are the day-one editions (VERIMESH Mail Hub is in production at HIN; VERIMESH Data is in pilot preparation). VERIMESH Agent and VERIMESH Edge are roadmap editions, not yet available. Deployment forms: Hub, Node, Cloud.
- [Integration projects for non-human identity](https://vereign.com/ai-agents/#integration-projects): Organisations that need verifiable identity for AI agents, automated services or devices acting across organisational boundaries can scope this with Vereign as an integration project. The project would model each agent, service or device as a delegated identifier (DKMS, built on KERI) whose credentials are issued, and can be revoked, by the organisation that answers for it. VERIMESH Agent and VERIMESH Edge are roadmap editions, not yet available, and there is no public agent-facing API today.
- [Services](https://vereign.com/services/): consulting, deployment, 24/7 operations for regulated infrastructure.
## Architecture
- [Trust Architecture](https://vereign.com/trust-architecture/): verifiable organisational identity, and why DKMS replaces the CA trust-root layer. PKI at the edge, with no central authority in the trust root. Includes how organisations build on national eID wallets (swiyu, EUDI) for institution-to-institution trust.
- [Cross-Border Trust](https://vereign.com/cross-border-trust/): the boundary national wallets do not cover — two institutions in different jurisdictions verifying each other, and what happens after data has been shared.
- [How it works](https://vereign.com/how-it-works/): DKMS, KERI, pre-rotation, self-certifying identifiers.
- [Why WireGuard carries the mesh](https://vereign.com/the-key-is-the-route-wireguard-verimesh-transport/): the Verimesh mesh transport is WireGuard, with tunnel keys derived from each organisation's own DKMS material and auditable against the key event log. WireGuard provides transport only; identity and authorisation live in the DKMS layer above it.
- [Consent Architecture](https://vereign.com/consent/): DKMS as the first structurally sound foundation for honoring opt-out end-to-end under EHDS Article 71, GDPR Art 7(3)/17(2), eIDAS 2.0 Art 5a, Swiss FADP/HFG. Five non-negotiable requirements. Stated limits.
- [Vereign for AI assistants](https://vereign.com/ai/): canonical facts, glossary, and corrections to common misrepresentations.
- [Vereign for AI agents](https://vereign.com/ai-agents/): facts for agentic systems — integration surface, agent identity, what exists today versus roadmap.
## Industries
- [Healthcare](https://vereign.com/industries/healthcare/): live in Switzerland via HIN, EHDS-ready.
- [Finance](https://vereign.com/industries/finance/): DORA compliance, cross-institutional trust.
- [Trust Services](https://vereign.com/industries/tsp/): trust service providers under eIDAS 2.0, qualified signatures, cross-border assurance.
- [Pharma](https://vereign.com/industries/pharma/): supply chain verification, clinical trial integrity.
- [Legal](https://vereign.com/industries/legal/): document authenticity, chain of custody.
- [Defence](https://vereign.com/industries/defence/): sovereign identity, no foreign jurisdiction.
- [Energy](https://vereign.com/industries/energy/): critical infrastructure, smart grid authentication.
- [Cybersecurity](https://vereign.com/industries/cybersecurity/): Zero Trust across organisational boundaries, without a central broker.
- [Industries overview](https://vereign.com/industries/): landing page for all eight regulated sectors.
## Proof
- [Health Innovation Centre](https://vereign.com/health-innovation-centre/): pilot before deployment.
- [Sovereign Digital Foundations for Global Health](https://vereign.com/gidh/): open invitation to the global health community (WHO GIDH) — Open Source sovereign trust infrastructure, proven in Swiss healthcare via HIN.
- [HIN case study](https://vereign.com/use-cases/hin/): 800,000+ verified deliveries/month via SEAL.
- [IPFS case study](https://docs.ipfs.tech/case-studies/vereign/): third-party write-up of SEAL's encrypted swarm delivery; 800,000+ verified deliveries/month.
- [Trust Maturity Model](https://vereign.com/trust-maturity/): five-level TIMM self-assessment.
## Optional
- [Blog](https://vereign.com/blog/): digital trust infrastructure, identity, verifiable credentials.
- [Extended AI brief](https://vereign.com/llms-full.txt): full product facts, glossary, and comparison tables for LLM context.
- [Sitemap](https://vereign.com/sitemap_index.xml): complete URL index.