Build & automate your business with NOAN's AI knowledge system. Collaborate with accurate AI assistants at every step of your business building journey.
This is the 2nd launch from NOAN. View more
NOAN
Launching today
Your company has thousands of documents, but only one version of the truth. NOAN turns the facts your business has approved such as pricing, positioning, policies, products, customers, and more into a verified, versioned source of truth available through API and MCP. Connect any model, agent, or app and give them all the same company facts, instead of letting each AI interpret your documents differently.
Free Options
Launch Team / Built With
I like the idea of separating company facts from the documents that contain them. Does NOAN keep a history of who changed each fact and why?
Is there a workflow for resolving conflicting facts before they reach an agent?
does it support custom integrations with existing google docs or notion databases for intial setup?
Dial
the fact-level permissions and drift detection answer above is solid for async channels where someone can wait for approval. our case is voice, the agent is mid-call and has maybe 800ms to answer, so there's no time to check for a pending approval. curious whether NOAN distinguishes "verified and stable" facts from "approved but still drafty" ones at read time, so a live agent could be configured to only pull the former and fall back to "let me check on that" for the rest
NOAN
@galdayan we use voice too! Our voice agent runs on the fact layer, our investors talk straight to her for instance too. Facts are either live or draft, it's about what is live on the API. So a voice agent would be a service using the API, as a result it's what's live that matters to it. It's a different way to think about how a business is run, your facts control the company and agents. If given write permissions it can also update facts or the contacts details it is talking to as well in real time.
NOAN
@galdayan facts are approved decisions. Our agents only ever answer questions if it can find the answer in our fact base. It will say outright that it doesnt have the answer if it cant find it. At which point a human gets flagged in the task manager so we can fill in the gap for next time. Our agents will never provide an answer that is not recorded as a fact.
The MCP setup caught my attention. Connecting it to Cursor or Claude Code that quickly sounds nice.
NOAN
@kyle_bennett6 it's really easy and means you can jump between models but it's always the same fact layer. I use Codex then claude code and each is always up to date and accurate.
The API and MCP support caught my attention. Having the same verified facts available across differnet tools sounds very practical.
NOAN
@magdalena_anderson yep, it's game changing. We're using a host of platforms with NOAN headless but they all call the same fact layer. You can have the non technical team on Cowork and your tech team on Codex and it's all calling the same facts. Let me know if you have any other questions, happy to answer.
i have been using separate tools for documentation and task tracking for years but having AI bridge both context saves so much back and forth.
NOAN
@charles_brewer90 Hi! Yes completely, that's what we thought too, you can also guarantee accuracy as your AI will call the facts rather than hit and hope on memory.