NOAN

Without a fact layer AI agents have to reason with marketing content and untrusted sources. NOAN fills that gap and gives you complete control over how your organisation's decisions are captured and acted on.

NOAN Features

One API for your verified facts, read by every agent, app and site.

  • A NOAN fact for a Team plan price, verified and approved, with its version history.

    Facts

    Verified, versioned truth about the business.

  • An API request for the pricing fact and its JSON response.

    API

    One key, over REST and MCP. Every agent, app and site reads the same fact.

  • A renewal agent’s steps, with a drafted reply waiting for approval.

    Agents

    Agents read the facts before they act, and wait for a person to approve what goes out.

  • A contact profile with tags and memos from a person, Claude and an agent.

    Network

    Every contact with their roles, tags and memos, readable by people and agents.

  • A task board shared by people and agents, with one task waiting on a person.

    Tasks

    One board for people and agents. A tag routes the work; an assignment approves it.

Frequently asked questions

What is a fact layer?

A single, trusted set of facts about your organisation that your team and your AI tools all work from. Each fact is verified, has an owner and keeps its version history, so you can see what changed and when.

How is this different from pointing an AI tool at our website and documents?

Your website and documents were written to persuade, and they often contradict each other. A fact layer holds the version your organisation has approved, so an agent answers from that version instead of from marketing copy.

What is Hex’s relationship with NOAN?

Hex is a NOAN integration partner. We run Hex on NOAN ourselves: it holds our fact layer, runs our agents and is our CRM.

Which tools can read the facts?

Anything that can call an API. NOAN exposes your facts over REST and MCP with a single key, so your website, your internal apps and AI assistants like Claude all read the same fact.

Do the agents act on their own?

Only as far as you allow. Agents read the facts before they act, and anything going out waits for a person to approve it. You decide which actions need that approval.

Where does an engagement start?

With the design. We work out what your fact layer needs to hold, where each fact comes from and who owns it. That gives you a blueprint and a roadmap. We then fill it in stages (foundations, then detail, then customer and sector knowledge), so each stage is useful before the next one begins. After that we plan the agents and roll it out to your team.

Who keeps the facts up to date after launch?

Your team does, with help. The blueprint names an owner for each kind of fact before we write any facts in. Rollout includes training and regular routines, so keeping facts current becomes part of how people work.

Can we see it working?

Yes, on our own site. The Advisor on hexdigital.com answers visitors from Hex’s fact layer and says plainly when it doesn’t know something. When a fact changes, a Content Steward agent drafts the page update for an editor to review.

What happens to our fact layer if we stop using NOAN?

You keep it. Your facts can be read out through NOAN’s API and moved to another system, and the blueprint that sets out how they are organised, where each one comes from and who owns it is a document you hold. The research and writing behind the facts doesn’t need redoing; the work in a move is reconnecting the website, apps and agents that read from NOAN, which we can scope with you.

Let's talk about your project

Get in touch to see how this could work for you.

Contact us