Side by side
Competitor claims last verified 1 November 2026| Dimension | NOAN | Curated Data |
|---|---|---|
| Purpose | Holds your company's own approved facts, like prices, policies and product details, so every agent reads the current version | Keeps the approved version of your policies, pricing and terms, so every AI assistant you connect answers from it |
| Source of truth | One current fact per block, written and verified by your team. A new version supersedes the last | One page per policy, definition or product detail, written as Markdown in the Open Knowledge Format, each with a named owner and an approval status |
| Who verifies | A named person on your team. Facts an agent writes can wait for a person to verify them before anything reads them | A reviewer approves each change before it is served. The previous approved version keeps answering until its replacement is signed off |
| Versioning and history | Every version kept, with who verified it and when. Time Travel shows your facts as they stood on any past date | Every version keeps its author, reviewer and approval time, with an audit log of approvals, rejections and membership changes |
| Permissions | Roles and fact permissions decide who sees and edits each area. Each API key is scoped further: read or write per resource, a list of allowed stacks, and fact changes held for approval | Each connection gets its own scoped key, limited to the classifications it is cleared to read, so customer-facing tools see only customer-safe pages |
| How agents access it | Remote MCP server (OAuth or an API key), REST API with an OpenAPI spec, and an open Agent Skill. Plain JSON from any language, no SDK needed | A hosted MCP server (browser OAuth or a scoped API token) and a REST v1 API with an OpenAPI contract |
| Where it fits | The fact layer under your agents, apps and site, read over MCP or REST | The approved answer behind the assistants your teams use, with pages for customer success, deal desk, support, sales, HR, legal and IT |
When to choose Curated Data
- You think in pages: a refund policy, a discount matrix or a set of plan entitlements, each written and approved as one document
- Your first job is approved answers behind your customer success, deal desk and support assistants
- You want your knowledge as plain Markdown files in an open format you can download as a bundle
- You want help filing and tidying drafts, which Curated Data offers as automatic organization on paid plans
When to choose NOAN
- You want each fact on its own, with its own verifier and version history, rather than a page that bundles many
- Different people and keys should see different areas of your facts
- Your website, internal apps and your own agents read the same facts as your assistants, over REST as well as MCP
- Your systems should react the moment a fact changes, through webhooks
The deeper comparison
Close peers: pages and facts
Curated Data and NOAN agree on what matters most: one approved version of each answer, a named person who signs off, every version kept, and agents that only ever read what was approved. Curated Data never serves a draft and keeps the last approved version live until its replacement is signed off. That is exactly the discipline agents need.
The honest difference is granularity and the developer surface. Curated Data is centered on pages: a document per policy or product detail, approved as a whole, in the open Markdown-based Open Knowledge Format. NOAN is centered on facts: each one versioned on its own with a named verifier, permissions by area and per API key, webhooks when a fact changes, and a REST API meant for apps and sites as well as assistants.
Using them together
Most teams should keep each answer in one place, since two places to approve the same refund window is how drift starts. If your support and deal desk assistants already answer from Curated Data pages, a clean split is those pages there and the facts your website, apps and own agents read in NOAN, with each one owned in exactly one of them.
Common questions
What is Curated Data?
Curated Data (curateddata.megacorp.company) keeps the approved version of your policies, pricing and terms as pages, each with a named owner. A reviewer approves each change, and AI assistants read only approved versions through a hosted MCP server or a REST API.
Is NOAN an alternative to Curated Data?
Yes. Both serve approved knowledge to agents over MCP and REST, with a named person approving each change and every version kept. Curated Data organizes it as pages, while NOAN versions each fact on its own and adds permissions by area, webhooks when a fact changes, and Time Travel to see your facts on any past date.
How do I give my AI agent verified facts about my company?
Keep your company's own facts in one place where a person verifies each one, then connect your agents to it. With NOAN, that is the remote MCP server at https://mcp.getnoan.com/mcp or the REST API at https://api.getnoan.com/v1.
Am I locked in to either one?
No. Curated Data stores pages as Markdown in the Open Knowledge Format and lets you download a bundle. NOAN keeps facts as plain text behind a REST API, and one GET exports everything.
Sources: Curated Data · Curated Data docs · Curated Data MCP · NOAN API spec · This page as Markdown · All comparisons
Next step
Connect your agent to verified facts
A remote MCP server for your company's own facts. Sign in over OAuth or send a NOAN API key. Install steps for Claude, ChatGPT, Cursor and Codex.
Plain REST with a bearer key, JSON in and out, from any language. Every endpoint is in the OpenAPI spec.
Or tell any agent: Read https://www.getnoan.com/setup.md and follow it.
See the fact layer with your facts in it
Every plan includes the API and MCP, and paid plans add unlimited keys. Start with one verified fact and build from there.