NOAN for Legal
Legal agents that cite the terms in force
Your standard terms, fallback positions, and approved claims live in NOAN as verified facts. Every agent that drafts, reviews, or answers reads the current version over MCP or REST, and every past version stays on the record.
Why legal agents cite the old version
Legal wording is precise, and it changes. A copy that was right last year can be wrong today.
Terms live in drafts
The current terms, the previous ones, and a few redlines sit side by side in a shared drive. An agent that searches them has no way to know which one is in force.
Positions drift
Your position on a common contract ask changes after a review. The sales team's assistant keeps the old one until someone remembers to tell it.
Answers need a source
When legal is asked why an agent said something, the answer has to be a dated source with an owner, not a paragraph in a prompt.
Your legal positions, one fact at a time
Examples, for illustration. Your own list depends on your business and your counsel, and each item is a fact a named person on your team verified.
Standard terms
Which version of your terms and privacy policy is in force, and since when.
Fallback positions
What your team will and will not accept on common contract asks.
Approved claims
What product and marketing copy may say, and the wording it must avoid.
Compliance answers
Where customer data is processed, and your standard answers for security questionnaires.
What your legal agents can do with them
Examples, for illustration. Any agent or assistant that can call MCP or REST reads the same verified facts.
Contract first pass
Flags clauses in an incoming contract that differ from your verified positions, for a lawyer to review.
Questionnaire answers
Drafts security and procurement questionnaire answers from the current compliance facts, for a person to check before they go out.
Claims checks
Checks marketing and sales copy against your approved claims before it ships.
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
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.
Permissions
Roles and fact permissions decide who sees and edits each area, so a sensitive area stays visible only to the people you choose.
Serve over MCP and REST
Claude, ChatGPT, Cursor and Codex connect over MCP. Internal tools and review workflows 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 the systems built on it can update 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
Does NOAN give legal advice?
No. NOAN holds the positions and wording your own team has verified and serves them to your agents. What goes into it stays with your lawyers.
How do we know which version an agent used?
Every fact carries who verified it and when, and every version is kept. Time Travel shows your facts as they stood on any past date, so you can see which version was current when an agent acted.
Can an agent change a legal fact on its own?
Facts an agent writes over the API can be held for a person to verify before anything reads them. API keys are scoped per resource, read or write, so a drafting agent can have read access only.
Can we keep some legal facts private?
Yes. Roles and fact permissions decide who sees and edits each area, so a sensitive area stays visible only to the people you choose.
Put your legal positions on verified facts
Start with the wording your agents quote most: your terms, your fallback positions, your approved claims. Every plan includes the API and MCP, and paid plans add unlimited keys.