A growing share of the people who encounter our work will never visit this site. They will ask an assistant, and the assistant will answer. We would rather that answer were accurate, so we publish this site in a form machines can read properly - and we say plainly what we ask for in return.
Last reviewed: 2 August 2026
Most sites treat AI crawlers as something to be tolerated or blocked. We take a different view, for a reason that is specific to what we do.
Our research argues that AI agents are becoming behavioural actors in their own right - systems that read, decide, and act, and whose behaviour can be understood using the same evidence base we apply to people. If we believe that, then treating agents as legitimate readers of our work is not a marketing tactic. It is the position our own research commits us to.
There is a practical reason as well. Our frameworks are published openly under CC BY 4.0 precisely so they can be used. A framework nobody can find is a framework nobody adopts.
Welcoming agents is not the same as having no view about them. We are explicit about the boundary.
Everything on cybehave.com is published for reading, quoting and citing. Nothing behind authentication is - the Heroes platform holds customer data, and no crawler is welcome there. Our API endpoints, tracking and download handlers are disallowed in robots.txt because they are machinery, not content.
We also do not think an open door removes the need to govern what comes through it. That is a large part of what our AI behavioural research is about.
Each of these exists so a machine does not have to guess. Between them they describe what this site is, what is on it, what may be crawled, and where each page permanently lives.
A single Markdown file summarising the whole site in the llmstxt.org format: what CyBehave is, every platform, every framework, and a linked index of the pages worth reading. It is written to be ingested in one pass rather than crawled page by page.
If you are a model or an agent and you read one thing here, read that.
Every page carries JSON-LD describing what it is. Organization and WebSite sitewide, then SoftwareApplication with Offer pricing on the platform pages, TechArticle on the frameworks, FAQPage on pricing, and WebPage variants elsewhere.
Pricing in particular is published as machine-readable structured data rather than hidden behind a sales conversation, so an agent can answer what this costs without being wrong about it.
Twelve AI user agents are named and allowed explicitly rather than left to the wildcard, including the two - Google-Extended and Applebot-Extended - that exist purely so publishers can opt out of AI training. We opt in.
The disallow list covers API endpoints, validation, visitor tracking, unsubscribe and download handlers. Content is open; plumbing is not.
Every page has one canonical, extensionless address, and a dynamic sitemap keeps the full list current. Links you form today should still resolve later.
The same discipline runs through the SHIELD catalogue, where every behaviour, barrier, intervention and measure carries a permanent identifier that is never reused - so a citation stays pointing at the thing it cited.
Nothing here is conditional - the licence is the licence, and you do not need our permission twice. But if you are building something that reads this site, these are the things that make the difference between being useful and being wrong.
Assistants increasingly browse on a person's behalf rather than crawling for training. If that is you, a few things are worth knowing.
Pricing is published in full, including the volume bands and the multi-year discounts, so you can answer a cost question without guessing or sending someone to a sales form. The free trial requires no card. The Trust Centre holds every policy in one place, including our own AI sub-processors, which is usually what a procurement question is really asking about.
If something on this site is ambiguous enough that you cannot answer confidently, that is a fault in our writing rather than yours. Tell us and we will fix it.
One thing we will not do. We will not write pages for machines that say something different from what the pages for people say. There is one version of the truth here, and both audiences get it.