npx -y @getnoan/wizard@latestTakes your key, wires Claude Code, Cursor, Codex and friends to the NOAN MCP server, installs the NOAN skill, and hands the seeding of an empty workspace to your assistant. The API below is what it, and everything else, runs on.
Using NOAN Headless
How it works
A bearer token and standard REST. If you can make an HTTP request, you can build on your facts.
- 01
Create a key
Settings > API > New key. Personal keys authenticate as you and inherit your roles and fact permissions, so a key can never read more than its owner can. The Free plan includes one key; paid plans include unlimited keys.
- 02
Read your truth
One GET returns verified facts as plain JSON, by block. Ground a page, a prompt, an app, or an agent in it. No SDK, no framework, any language.
- 03
Write back, safely
Create tasks, contacts, notes, and assets, or update facts. Every write is attributed to the key's owner, and every fact change is versioned with full history.
# Read your verified facts. That's the whole integration.
curl "https://api.getnoan.com/v1/facts?block_slug=<your-block-slug>" \
-H "Authorization: Bearer $NOAN_API_KEY"
# items[].content are your facts, as plain JSON.
# Feed them to any model, app, or page.Self-serve plans include 200 requests per minute; Enterprise raises the limit.
What's on the API
The whole workspace, addressable
Everything below is live in the OpenAPI spec. Facts are the core; the rest is the workspace around them.
Facts
The verified truth, one fact per block. Writing replaces the block's fact as a new version, so read, merge, and post the complete document.
Stacks & Blocks
The ontology itself. Create custom stacks and blocks programmatically to shape how your business knowledge is structured.
Contacts
The headless CRM. Every relationship with its context, readable and writable by your apps and agents.
Tasks
The control plane. Dispatch work, claim it, move status, and link tags, assignees, and contacts. This is the board agents run from.
Notes
Captured knowledge: meeting notes, ideas, and records your assistant and agents can search and write.
Assets
What you and your agents produce: decks, posts, articles, videos. Versioned like everything else.
Tags
The routing system. Tags carry usage instructions and act as triggers for agents watching the board.
Me
Who this key is: the project and identity it acts as, and therefore what it is allowed to touch.
Webhooks
Facts that tell you when they change
Keeping what you build in sync used to mean polling the API on a schedule. Webhooks flip that around: the moment a fact, a note, or a contact changes, NOAN pushes the event to your endpoint, and what you built moves to the new truth.
Event-driven, not polling
Your app reacts the instant a fact changes instead of asking for news on a timer. Less latency, fewer wasted calls.
Change once, everything moves
Update a fact in NOAN and every site, app, and agent you run on the API can refresh or re-ground at the same moment.
Read, write, react
The API already reads and writes facts. Webhooks add the third part: NOAN tells you when something changed, and each event names what.
Rebuild a page when its source fact changes, clear a cache, re-ground a running agent, or start a downstream workflow the second the underlying fact moves.
Turn them on in Settings, under Your Project, then Integrations: set the endpoint that receives events, optionally require a valid TLS certificate with Verify Endpoint Certificate, and watch every delivery land in the live log with its HTTP status, event type, any error, and a timestamp. The flow above is a sample.
What you can build with it
Once your business is facts behind an API, almost anything can stand on top, and changing a fact once updates every one of them.
Websites that never go stale
This site is the demo: our pricing page renders live from the fact base. Point Lovable or your own stack at the API and your site reads truth, not copy.
Internal apps and portals
Dashboards, client portals, investor views. Anyone on the team can build one for their own use case, on any stack, with their own key.
Integrations
Ground Clay outbound in your facts, feed Zapier flows, or wire your existing systems to read and write the same truth.
Whatever ships next
The API is plain REST and model-agnostic. Nothing you build is coupled to one vendor's assistant, model, or framework.
What agents can do with it
The API treats agents as first-class citizens: grounding reads, a task-queue control plane, and attributed, versioned writes.
See how to build an agentGround at run time
Agents read facts live before they act, so outputs are built from current truth, not a stale prompt.
Work the task queue
A tag says which agent a task is for; assignment is the permission to act. Agents claim work, do it, and report back on the board.
Write back
Agents record notes, enrich contacts, save assets, and propose fact updates that wait for human verification.
Connect over MCP
Claude, ChatGPT, and other assistants mount the same brain over MCP, so chat surfaces and coded agents share one truth.
The Fact Infrastructure For Agentic Companies.
API & MCP works with
- Claude
- OpenAI
- LLaMA
- Mistral
- Cursor
- Lovable
- Replit
- Clay
- Hermes
- Paperclip
- and anything that speaks REST or MCP
Every answer grounded
Any model, any agent, any app makes the same call: read the fact, answer from it, and hand back the receipt. The price below is our live Team plan, read through the API as the section plays.
The docs live at one URL
The full OpenAPI spec is public. Read it yourself, or hand it to your AI assistant with an API key and let it build the client for you.
https://api.getnoan.com/openapi.jsonChoosing between a fact layer and agent memory? Read agent memory vs verified facts, or how NOAN compares to Mem0 and Zep.
USE THE API & NOAN POWERS YOUR WHOLE STACK - BECOMING YOUR CMS, CRM, & CONTEXT LAYER.
Build on your facts
Every plan includes the full API and MCP, and paid plans add unlimited keys. Create a key and make your first request in minutes.