Facts and blocks now carry a classification you can read over the API and MCP
Every approved fact gets a type, secondary types and subject, available on REST and MCP, for builders working with NOAN's facts.
Your facts have always held rich detail in their text. Now they carry structure to match: until today, sorting them by what they were about, whether a fact described a person, a price, a product or a policy, meant reading each one and deciding for yourself, and agents built on NOAN worked from the text alone with nothing structured to sort or route on.
What's new
- Approved facts are classified automatically. When a fact is approved, NOAN assigns it a primary type, secondary types and a subject.
- Managed blocks keep a fixed type. A managed block carries its own classification type, which becomes the primary type of its fact.
- Read it on REST and MCP. Facts and blocks now expose their classification over the REST API and MCP, so an agent can filter and group facts by what they are about.
Why it matters
When an agent reads a project's facts, a classification tells it which ones are pricing, which are people, which are policy, without parsing the text. That makes it far easier to build something that acts on the right facts and leaves the rest alone.
Where to find it
Classifications come back on facts and blocks through the REST API and MCP. See the API docs at api.getnoan.com.
Good to know: only approved facts are classified, and the classification is set by NOAN, not something you override.