Hjarni

Files and knowledge

Hjarni for AI agents. Bring approved knowledge into focus.

Search and read Hjarni notes through Agent200. Prepare knowledge briefs grounded in retrieved note content and explicit source identity.

About Hjarni

With the Hjarni connector, your agent searches and reads notes with the project’s Agent200 API key, so no separate Hjarni account or key is needed. It can search, list and read notes, and browse containers and tags, using only the tools your project allows.

Hjarni is a note-taking and knowledge management service.

Tools

What your agent can do in Hjarni.

Each tool is a capability the model can call. You decide which ones a project allows, and your Agent200 API key reaches them.

  • Search knowledge

    Read
    hjarni_search

    Search notes, folders and tags available through the project’s Hjarni tools.

  • List notes

    Read
    hjarni_list_notes

    Find notes available within the selected accessible scope.

  • Read a note

    Read
    hjarni_get_note

    Retrieve an identified note and its returned content.

  • List folders

    Read
    hjarni_list_containers

    Find accessible containers and their returned metadata.

  • Read a folder

    Read
    hjarni_get_container

    Retrieve details of one identified container.

  • List tags

    Read
    hjarni_list_tags

    Find tags available through the project’s Hjarni tools.

Control

Limits you can set.

You decide what your agent may do in Hjarni, and Agent200 runs every call within those limits.

  • Turn single tools on or off

    Let the agent search and read notes, and switch off hjarni_get_note if it should only see search results and lists.

  • Restrict what the agent reaches

    Choose the endpoints a project may use, for example searching and listing notes but not reading containers. A call outside them is refused.

Get started

Connect Hjarni
in two steps.

  1. 1

    Set up the SDK

    Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.

    agent.js
    Conceptual example
    Set up the SDK with the Agent200 API key
    // One Agent200 API key covers every connector enabled for the project.
    const agent200 = new Agent200({
      apiKey: process.env.AGENT200_API_KEY,
    });
  2. 2

    Run with the Hjarni tools

    Name the model and the tools. The model decides which Hjarni tools to call, and Agent200 executes them with your Agent200 API key.

    run.js
    Conceptual example
    Run a request with the connector's tools
    const result = await agent200
      .user("user_123")
      .run({
        model: "openai/gpt-5.6-sol",
        input: "Search my notes for the pricing research",
        tools: ["hjarni"],
      });
    
    console.log(result.output);

For agents

Instructions for AI agents.

Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the Hjarni connector and how to use it.

Agent brief
Connector: Hjarni, through Agent200. In code: "hjarni".
What it does: Search and read Hjarni notes through Agent200. Prepare knowledge briefs grounded in retrieved note content and explicit source identity.
Page: https://www.agent200.com/connectors/hjarni/

1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs.
2. Agent200 reaches Hjarni with the project's Agent200 API key. No separate Hjarni key is needed.
3. Read tools: hjarni_search, hjarni_list_notes, hjarni_get_note, hjarni_list_containers, hjarni_get_container, hjarni_list_tags. Name "hjarni" in the tools of a request; the model decides which tool to call.
4. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it.
5. Before a write, confirm with the user, unless they asked for that exact change.
6. For setup with a specific framework, follow its guide:
   https://www.agent200.com/connectors/hjarni/framework/claude/
   https://www.agent200.com/connectors/hjarni/framework/chatgpt/
   https://www.agent200.com/connectors/hjarni/framework/claude-code/
   https://www.agent200.com/connectors/hjarni/framework/muse/
   https://www.agent200.com/connectors/hjarni/framework/grok-bot/
   https://www.agent200.com/connectors/hjarni/framework/openai-dots/
   https://www.agent200.com/connectors/hjarni/framework/claude-duet/
   https://www.agent200.com/connectors/hjarni/framework/hermes-agent/
   https://www.agent200.com/connectors/hjarni/framework/openclaw/

The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/

This page is also available as Markdown, for agents and LLMs: /connectors/hjarni.md

Guides

Use Hjarni with the AI you build on.

Step-by-step setup for Hjarni with a specific model, assistant or agent framework.

FAQ

Hjarni and Agent200, answered.

Do I need a separate Hjarni key?

No separate Hjarni key is needed for this Agent200 route. Use the project’s Agent200 API key and enable the Hjarni tools.

Does search read the full note?

Search finds candidate notes. Read the selected note before using its body in a brief; cite the returned note identity and distinguish source text from suggestions. Hjarni MCP tool catalog.

Can this workflow edit Hjarni?

The listed tools are read operations. A proposed change in the brief does not create, edit or delete a note.

Why might a note be missing?

Check project tool enablement, the selected note ID, search scope and pagination. Do not infer that an inaccessible or unreturned note does not exist.

Which identifiers should code call?

The page lists Agent200 catalogue identifiers. Inspect the runtime’s advertised tool names and input schemas before implementation; Hjarni’s own MCP tool names are a separate provider contract.

  • Google Drive

    Google Drive

    Find, read and organize the files in each user's Drive.

    Managed OAuth Files and knowledge
  • OneDrive

    OneDrive

    Search, read, upload and share OneDrive files, including Word, Excel and PowerPoint documents, on behalf of each of your users.

    Managed OAuth Files and knowledge
  • Dropbox

    Dropbox

    Search, read, upload and organize Dropbox files, and create shared links, on behalf of each of your users.

    Managed OAuth Files and knowledge
  • Notion

    Notion

    Search, read and write Notion pages and databases on behalf of each of your users.

    Managed OAuth Files and knowledge
200 OK

Start with Hjarni.
Your agent does the rest.

Your agent reaches Hjarni with your Agent200 API key. No provider key to collect, store or rotate.

Book a demo.
See it in action.

Tell us who you are, then pick a time for a 1:1 session with an expert from our team.

We use your details only to email you about Agent200. See the Privacy Policy.

Pick a time. We'll take it from there.

A 1:1 session with an expert from our team, about what you are building.

Open in Calendly (opens in a new tab)