NOAN for IT
IT agents that know today's setup
Access rules, approved software, and setup steps live in NOAN as verified facts. Every IT assistant and agent reads the current version over MCP or REST, and webhooks tell your systems the moment one changes.
Why IT agents give yesterday's answer
IT answers go stale quietly. A tool is retired, a process moves, and the instructions everywhere else stay the same.
Instructions in every wiki
Setup guides, access rules, and the approved software list live in wiki pages, tickets, and old chat threads. An agent that searches them finds every version at once.
Retired tools come back
When you replace a tool, the old instructions keep getting quoted until every copy is found and fixed.
Access is not a guess
Who can request what, and who signs it off, is not something an agent should work out from an old thread.
Your IT answers, one fact at a time
Examples, for illustration. Your own list depends on your systems and your team, and each item is a fact a named person on your team verified.
Approved software
Which tools are approved for what, and which ones are retired.
Access rules
Who can request access to which systems, and who signs it off.
Setup and devices
Laptop setup steps, supported devices, and how to get a replacement.
Security contacts
Where to report a security issue, and who to contact for each system.
What your IT agents can do with them
Examples, for illustration. Any agent or assistant that can call MCP or REST reads the same verified facts.
Help desk answers
Answers employee IT questions from the current setup and software facts, and passes the request to a person when the facts run out.
Access requests
Explains who signs off which access, from the current access facts, before a request goes to the right person.
Coding agents
Claude Code, Cursor and Codex read your approved tools and internal conventions over MCP while they work.
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
MCP clients sign in with OAuth or send a NOAN API key as a bearer token. Scripts, internal tools, and services read the same facts over REST.
Scoped keys
API keys are scoped per resource, read or write, can be limited to a list of allowed stacks, and can hold fact changes for a person to verify.
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 do our agents connect to NOAN?
MCP clients such as Claude, ChatGPT, Cursor and Codex connect to https://mcp.getnoan.com/mcp and sign in with OAuth or send a NOAN API key as a bearer token. Anything else uses the REST API at https://api.getnoan.com/v1, described in the OpenAPI spec at https://api.getnoan.com/openapi.json.
How do we control what each agent can read and write?
API keys are scoped per resource, read or write, can be limited to a list of allowed stacks, and can hold fact changes for a person to verify. Every key acts as the person who created it, narrowed further by its own scopes and allowed stacks.
How do other systems find out when a fact changes?
Webhooks. NOAN sends an event, such as fact.updated, to an endpoint you choose whenever a fact changes, and the app shows every delivery in a live log.
Can we get our facts out again?
Yes. Your facts are plain text behind a REST API, and one authenticated request exports them.
Put your IT answers on verified facts
Start with the questions your help desk answers every day: access, software, setup. Every plan includes the API and MCP, and paid plans add unlimited keys.