Getnoan NOAN OpenAPI

Name: NOAN OpenAPI API
Brand: NOAN OpenAPI
Availability: InStock

★ Only Publicly Available OpenAPI DocumentProductivityNote Takingbearer13 EndpointsREST

For Agents

Search NOAN assets and stacks, create contacts, notes, facts, and tasks, and add blocks to a stack through a Bearer-authenticated knowledge API.

Install Jentic One Beta

Connect the NOAN OpenAPI to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the NOAN OpenAPI, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with NOAN OpenAPI API.

Authenticate and resolve the current account through GET /api/me

Search NOAN assets, stacks, and blocks with full-text-style queries

Create and update contacts and append notes to them

Create blocks inside an existing stack to extend a structured document

GET STARTED

Start building with NOAN OpenAPI API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for the NOAN API, keeping it validated and agent-ready. NOAN is a structured knowledge and business-context platform organised around assets, stacks, blocks, contacts, notes, facts, and tasks. The 13-endpoint REST API lets agents search assets, stacks, and blocks; manage contacts and the notes attached to them; create blocks inside stacks; and create facts, notes, and tasks. Authentication is HTTP Bearer using a per-account access token. It is suited to AI workflows that need to read and write structured business knowledge.

Use Cases

Patterns agents use NOAN OpenAPI API for, with concrete tasks.

★ Meeting Capture into Structured Knowledge

Turn meeting transcripts into structured NOAN content by creating contacts, notes, facts, and tasks for each takeaway. The integration calls POST /api/contacts, POST /api/contacts/{contactId}/notes, POST /api/facts, and POST /api/tasks. Replaces ad-hoc note-taking that gets lost between tools.

Call POST /api/contacts to create attendee records, POST /api/notes for the summary, and POST /api/tasks for each follow-up identified in the transcript.

Knowledge Search Endpoint

Build a sidebar that searches the connected NOAN account from another tool. The integration calls GET /api/assets, GET /api/stacks, and GET /api/blocks with a query string. Useful for surfacing prior business context inside AI products without copying data out.

Call GET /api/stacks?query=launch and GET /api/blocks?query=launch in parallel and merge the results into a single search result list.

Stack Authoring Pipeline

Programmatically grow an existing NOAN stack by appending new blocks generated by an agent. The integration calls POST /api/stacks/{stackId}/blocks. Useful when a long-running process produces structured business artefacts that need to live inside NOAN rather than a separate document.

Call POST /api/stacks/{stackId}/blocks with a structured block payload generated from a meeting summary.

AI Agent Knowledge Curator

An AI agent acts as a curator that captures meeting notes, identifies relevant contacts, and writes them into NOAN automatically. The agent uses Jentic's intent search to discover the right write operation rather than reading docs, and Jentic isolates the Bearer token. Time-to-first-write drops from hours to minutes.

Search Jentic for 'create a NOAN note', load the schema for POST /api/notes, and write a structured note summarising the latest meeting transcript.

Key Endpoints

13 endpoints — jentic publishes the only available openapi specification for the noan api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/api/me

Get authenticated user data

GET

/api/stacks

Search stacks

POST

/api/contacts

Create a contact

POST

/api/contacts/{contactId}/notes

Add notes to a contact

POST

/api/stacks/{stackId}/blocks

Append a block to a stack

POST

/api/notes

Create a note

POST

/api/tasks

Create a task

GET

/api/me

Get authenticated user data

GET

/api/stacks

Search stacks

POST

/api/contacts

Create a contact

POST

/api/contacts/{contactId}/notes

Add notes to a contact

POST

/api/stacks/{stackId}/blocks

Append a block to a stack

POST

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

NOAN Bearer access tokens are stored encrypted in the Jentic vault. Jentic injects the Authorization header on each call so tokens never enter the agent's prompt or memory.

Intent-based discovery

Agents search Jentic with intents like 'create a NOAN note' or 'search NOAN stacks' and Jentic returns the matching operation with its input schema, removing the need to read NOAN's docs.

Time to first call

Direct NOAN integration: half a day to a day to wire up Bearer auth and the search-plus-create flow. Through Jentic: under 30 minutes using search, load, execute.

FAQs

Specific to using NOAN OpenAPI API through Jentic.

Why is there no official OpenAPI spec for NOAN?

NOAN does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call the NOAN API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the NOAN API use?

NOAN uses HTTP Bearer authentication. The Authorization header carries the per-account access token, which Jentic stores encrypted in its vault and injects automatically at execution time so the token stays out of the agent context.

Can I create a contact and attach notes with the NOAN API?

Yes. Call POST /api/contacts to create the contact and POST /api/contacts/{contactId}/notes to attach one or more notes. Use PATCH /api/contacts/{contactId} to update profile fields later.

What are the rate limits for the NOAN API?

NOAN does not encode rate limits in the spec. Plan for low-volume control-plane usage around 5 requests per second per access token and back off when 429 responses appear; the response body usually includes a retry hint.

How do I search NOAN content through Jentic?

Search Jentic for 'search NOAN stacks', load the schema for GET /api/stacks, and execute with a query string. You can run the same flow against GET /api/assets and GET /api/blocks to cover the full content surface.

Can I append a block to an existing NOAN stack?

Yes. Call POST /api/stacks/{stackId}/blocks with the block payload to append a new block to a stack. This is the recommended way for an automated workflow to extend an existing structured document.

Getnoan NOAN OpenAPI

Connect the NOAN OpenAPI to your agent

Capabilities

Start building with NOAN OpenAPI API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs