canonical: https://jentic.com/apis/getnoan.com/getnoan # Getnoan NOAN OpenAPI 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. ## For AI agents Search NOAN assets and stacks, create contacts, notes, facts, and tasks, and add blocks to a stack through a Bearer-authenticated knowledge API. ## Scope Does not handle real-time collaboration, document export, or AI inference - use for structured knowledge capture and search only. ## Capabilities - 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 - Create facts that capture structured business statements for later retrieval - Create stand-alone notes and tasks tied to the authenticated account - List the tags available across the account for downstream filtering ## Use cases ### 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. Example prompt: 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. Example prompt: 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. Example prompt: 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. Example prompt: 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 | 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 | ## Key resources - **Auth** — Resolve the authenticated user via `/api/me` - **Assets** — Search assets stored under the account - **Stacks and Blocks** — Search stacks and blocks and append new blocks to an existing stack - **Contacts** — Search, create, update, and append notes to contacts - **Notes and Facts** — Create stand-alone notes and structured facts - **Tasks** — Create tasks tied to the authenticated account - **Tags** — List the tags available across the account ## Why Jentic - **Setup:** Wiring NOAN by hand means setting its bearer auth and shaping payloads for stacks, blocks, contacts, notes, and tasks across its endpoints yourself. Through Jentic you install once, import the NOAN OpenAPI from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** NOAN mixes collection creates like `/api/notes` with paths that name a stack or contact id, so you limit the agent to the operations it needs, such as creating a note or reading stacks. Because you pick the operation set, writes like adding a task are not reachable unless you add them. - **Credential handling:** Your NOAN access token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'create a NOAN note' or 'list knowledge stacks', and Jentic returns the matching NOAN operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Notion API** — Block-based knowledge platform with similar stack and block primitives - **Coda API** — Document-and-table hybrid platform with structured row APIs - **Asana API** — Task-tracking platform that pairs with NOAN for execution after capture ## FAQ ### 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 with Jentic One, the self-hosted execution layer. ### 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. ### Can I limit what my agent is allowed to do with the NOAN API? Yes. Because Jentic One is self-hosted, you decide which NOAN operations the agent can reach, so you can grant it just POST `/api/notes` and GET `/api/stacks` while leaving everything else off. Writes such as POST `/api/tasks` or POST `/api/contacts` stay unreachable unless you add them to the agent's operation set, and the access token is injected by your own instance at execution time rather than exposed to the agent. Your rules alone determine the operations and credentials the agent may use.