NOAN is the fact layer for agentic business. It takes the facts a company has approved — pricing, positioning, policies, products, customers, and more — and turns them into a verified, versioned source of truth that is served through one API and MCP. The product is built for anyone who wants their models, agents, and applications to run on the same company facts rather than each AI interpreting the company's documents in its own way. Verity, the assistant on the NOAN site, is the product demonstrating itself: give her your work email and she reads your website, draws your company graph, and turns it into your workspace.
The problem NOAN addresses is that most companies have thousands of documents but only one version of the truth. Documents are not facts. A document is something an AI can read and interpret, and different models and agents will pull different conclusions from the same pile of material. NOAN draws a clear distinction between a fact and memory: a fact is something true about your company that is approved, versioned, and served from one API, whereas memory is what an AI picks up along the way and nobody signed off on. When every model, agent, and app is fed the same approved facts, they all run from the same source of truth instead of letting each AI interpret your documents differently. That is why the product is described as the fact layer for agentic business: the facts, not the interpretation around them, become the thing everything else is built on.
The core of NOAN is the fact itself. According to the product, a fact is something true about your company: it is approved, it is versioned, and it is served from one API. That combination matters because it gives the business a controlled, authoritative record of what is true — not a draft, not a document open to interpretation, but an approved statement that carries a version. The approved facts NOAN works with include pricing, positioning, policies, and products, as well as customers. Instead of scattering that information across thousands of files, NOAN collects it and serves it through the NOAN API, so anything that needs company knowledge can request it from a single source rather than re-reading a document set and forming its own view.
Through the NOAN API and MCP, those facts can be plugged into any model, any app, and any agent. This is the other half of the product's promise: the fact layer is not tied to a single assistant or a single vendor. Because the facts are exposed through an API and through MCP, any model, agent, or app that connects can run from the same source of truth. In practice this means a company can give all of its AI systems the same company facts, rather than maintaining a separate and potentially conflicting understanding of the business inside each one. The line "Any model, any agent, any app — same facts, one API" summarizes how NOAN positions exactly this capability.
Every company's facts build a brain — its company graph. The company graph is how NOAN describes the result of collecting a company's approved facts: a connected representation of the business drawn from the facts themselves. Verity is the assistant that creates and works with it. She introduces herself with "I'm Verity. NOAN is the fact layer for agentic business. Give me your work email and I'll read your site and show you your company graph." When you provide your work email, Verity reads your site, draws your company graph, and makes it your workspace, so the graph is not just a picture of the business but the working place where the company's facts live.
NOAN's approach is to make the facts your business has approved the thing that everything else runs on. The workflow starts with your website and your work email: Verity reads the site and shows you your company graph, which becomes your workspace. From there, the approved facts are versioned and served from one API, and the same facts are available to your models, agents, and apps through the API and MCP. The distinguishing idea is the split between facts and memory: facts are approved and versioned by the business, while memory is whatever an AI happens to pick up along the way and nobody signed off on. By serving only the former, NOAN concentrates on the facts themselves rather than the surrounding interpretation, and every agent that connects to the fact layer inherits the same version of the truth. The site frames this as your company as verified facts, behind one API, with your site and agents running on what's true.
The benefit NOAN describes is consistency. When any model, any agent, and any app all draw from the same facts, they all run from the same source of truth, which removes the situation where each AI interprets your documents differently. Approved facts also carry versions, so the record of what is true has a history rather than being a static snapshot in a document nobody controls. Because the facts are exposed through one API and MCP, connecting a new model, agent, or app does not require rebuilding the company's knowledge from scratch — the connection simply plugs into the existing fact layer and runs on the same approved facts as everything else.
Concrete scenarios follow directly from how NOAN is described. A company wants its AI agents to answer with approved pricing, positioning, and policies rather than whatever a model inferred from a document set, so it gives those agents access to NOAN's facts. A team building an application needs the company's products and customers represented consistently, so it connects through the NOAN API and reads the same facts the rest of the business uses. An organization that runs several models or agents wants them to agree, so MCP and the API let each one connect to the fact layer. And a business just starting with NOAN gives Verity its website and its work email, watches her draw the company graph, and begins working from a verified set of facts in a workspace built around them.
NOAN speaks to businesses that want their AI systems grounded in verified company facts. It is aimed at teams using models, agents, and apps, which the Product Hunt listing describes under API, Developer Tools, and Artificial Intelligence, and it fits companies that already have thousands of documents and need one version of the truth. The integrations described are the NOAN API and MCP: any model, any agent, and any app can connect through them. The product is experienced on the web through the NOAN site, where Verity assists you, and the site includes a classic version, a "How does it work?" page, and a pricing page with an option for existing subscribers to sign in. On pricing, the site states that everything is free except the facts.
NOAN's primary value proposition is simple to state: your company has thousands of documents, but only one version of the truth, and NOAN is the fact layer that makes that truth approved, versioned, and available to every model, agent, and app through one API. With Verity reading your site and drawing your company graph, the facts your business has signed off on become the single source of truth that your site and agents run on.