Every question, and where its answer is.
- Questions, each answered in full
- 49
- Subjects, one page of answers each
- 7
- Hop from this page to any answer
- 1
These are the questions asked often enough to be worth publishing. Anything specific to your estate is a reply rather than a page.
ask it directlyThe subjects
What Token Observe is
The category, what the product does, what it deliberately is not, who it is for, and what stage it is actually at.
- What is Token Observe?
- What is Token Observe not?
- How does Token Observe work out what our AI actually costs?
- Is Token Observe the same product as AgentControl Plane?
- What does agent action assurance mean, and is it still what Token Observe leads with?
- Who is Token Observe for?
- What does Token Observe include?
- What stage is Token Observe at, and can it run production-critical workloads?
How it works
The request path step by step: how an agent is onboarded, what happens inline, what streaming and failover do, and what happens when something is unavailable.
- How does an agent start routing through Token Observe?
- What actually happens on one governed request?
- How much latency does Token Observe add?
- Does streaming work, and do policies still hold on a stream?
- What happens to our agents if Token Observe is down?
- What happens when a model provider fails?
- How are tools and MCP servers governed?
Security and threat model
The threat model, key custody, injection and redaction limits, whether the audit log can be rewritten, vulnerability disclosure, and what has not been tested.
- What is Token Observe’s threat model?
- Where do provider API keys live, and what stops Token Observe leaking them?
- How does Token Observe handle prompt injection, and how good is the detection?
- What are the limits of Token Observe’s redaction?
- Can an administrator rewrite the audit log?
- What does off-box anchoring not prove?
- Has Token Observe had an independent penetration test?
- How do we report a vulnerability, and what happens next?
- Does the vendor see our prompts?
- Who inside our organisation can read prompts and traces?
Compliance and evidence
EU AI Act, ISO/IEC 42001, NIST AI RMF and OWASP mappings, what an evidence export proves, retention and erasure — and which certifications do not exist.
- Does Token Observe make us compliant with the EU AI Act?
- Do you have SOC 2, ISO 27001 or ISO 42001 certification?
- How does Token Observe map to ISO/IEC 42001 and the NIST AI RMF?
- Are evidence exports signed?
- How does Token Observe map to the OWASP LLM and agentic top tens?
- What are the retention and erasure controls, and what do they not cover?
Deployment and operations
What it runs on, how long onboarding takes, backup and restore, upgrades and rollback, air-gapped installs, and why there is no high-availability topology.
Licence, pricing and support
The source-available licence, how the product is metered, the thirty-day evaluation, the support model, and what procurement has to accept in writing.
Alternatives and adjacent tools
Where Token Observe sits against gateways, observability, security platforms and identity products — and the case for and against building it yourself.
- How is Token Observe different from an LLM gateway?
- We already have LLM observability. What does Token Observe add?
- How is Token Observe different from an AI security platform or an AI firewall?
- How is Token Observe different from an agent identity or control-tower product?
- Why not build this ourselves?
If the question that decides it for you is not one of these, it is the one worth sending. There is no form in the way and no qualification step behind it.
Ask it directlyThe questions a page cannot answer.
Write to hello@tenhaw.com with what your agents do, which providers they call and what would have to be true for you to put something in front of them. James Rooney replies. You will get a straight answer about whether Token Observe fits, including when it does not.
no form · no qualification step · no sales desk · the other three ways in