NOAN for Support
Support agents that quote this week's policy
Your refund window, plan prices, and escalation rules live in NOAN as verified facts. Every support agent and assistant reads the current version over MCP or REST, and when a fact changes, they all change with it.
Why support agents quote last year's policy
The agent is rarely the problem. The policy it was given is a copy, and the copy is old.
Policies live in copies
The refund policy sits in a help center article, a saved reply, a system prompt, and a doc someone pasted into a bot last spring. Each copy ages on its own.
Prices change, prompts don't
When a plan price or limit moves, nothing tells the agent. It keeps quoting the number it was given until a customer points it out.
Nobody can say who decided
When an answer is wrong, the team has to work out where it came from. A pasted paragraph has no owner and no date.
Your support answers, one fact at a time
Examples, for illustration. Your own list depends on your product and your policies, and each item is a fact a named person on your team verified.
Refunds and returns
The refund window, who qualifies, and what happens to a partly used month.
Plans, prices and limits
What each plan costs and includes, so no agent quotes a price you retired.
Response times and escalation
Your response times by plan, and the point at which a conversation goes to a person.
Known issues and workarounds
The current status of a known problem and the workaround to offer, updated when it changes.
What your support agents can do with them
Examples, for illustration. Any agent or assistant that can call MCP or REST reads the same verified facts.
Ticket replies
Drafts answers from the current policy facts, and hands the conversation to a person when no fact covers the question.
Chat on your site
Quotes the plan prices and limits your team verified, not a copy of the pricing page from last quarter.
Saved reply checks
Compares saved replies and help articles with the current facts and flags the ones that have drifted.
Every one of them is built on the same three primitives. See how to build your own, or start from the open-source agent pack.
Verify once. Every agent reads the current version
NOAN is the fact infrastructure for agentic companies: one API, over REST and MCP, for the verified facts about your business.
Verify
A person on your team verifies each fact, and the fact carries who verified it and when. Facts an agent writes over the API can be held for a person to verify before anything reads them.
Version
Every version is kept. Agents read the current one, and Time Travel shows your facts as they stood on any past date.
Serve over MCP and REST
Claude, ChatGPT, Cursor and Codex connect over MCP. Help desk bots, internal tools, and your site read the same facts over REST.
Webhooks when a fact changes
NOAN sends an event to an endpoint you choose the moment a fact changes, so you can refresh a cache or re-ground a running agent without polling.
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.
Common questions
How does NOAN stop a support agent quoting an old price?
The agent reads the price from NOAN when it answers, over MCP or REST, instead of from a copy in its prompt. When your team verifies a new price, the old version stays on the record and every agent reads the new one from then on.
Do we have to replace our help desk or chat tool?
No. NOAN sits underneath the tools you already use. Anything that can call an MCP server or a REST API can read the same verified facts, and webhooks tell your systems when a fact changes.
Can an agent write facts?
Yes, over the API, and those writes can be held for a person to verify before anything reads them. API keys are scoped per resource, read or write, and can be limited to a list of allowed stacks.
Can we see what an agent was told when it answered a customer?
Yes. Every version of every fact is kept with who verified it and when, and Time Travel shows your facts as they stood on any past date.
Put your support answers on verified facts
Start with the policies your agents quote most: refunds, prices, response times. Every plan includes the API and MCP, and paid plans add unlimited keys.