NOAN Headless

Your business, as an API

Programmable access to your fact base and workspace: plain REST, a bearer key, and unlimited keys on every plan. It is the same API this website, our agents, and our apps run on.

Verity Explains the API

How it works

A bearer token and standard REST. If you can make an HTTP request, you can build on your facts.

  1. 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. Unlimited keys on every plan.

  2. 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.

  3. 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 verified facts
# 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

GET · POST · versions

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

GET · POST

The ontology itself. Create custom stacks and blocks programmatically to shape how your business knowledge is structured.

Contacts

GET · POST · PATCH · notes

The headless CRM. Every relationship with its context, readable and writable by your apps and agents.

Tasks

GET · POST · PATCH · tags, assignees, contacts

The control plane. Dispatch work, claim it, move status, and link tags, assignees, and contacts. This is the board agents run from.

Notes

GET · POST

Captured knowledge: meeting notes, ideas, and records your assistant and agents can search and write.

Assets

GET · POST · versions

What you and your agents produce: decks, posts, articles, videos. Versioned like everything else.

Tags

GET

The routing system. Tags carry usage instructions and act as triggers for agents watching the board.

Me

GET

Who this key is: the project and identity it acts as, and therefore what it is allowed to touch.

Build on it

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.

Agents

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 agent

Ground 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 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.

API docs
https://api.getnoan.com/openapi.json

Build on your facts

Every plan includes the full API, MCP, and unlimited keys. Create a key and make your first request in minutes.