Hjarni + OpenAI Dots

Build a Hjarni reader with OpenAI Dots Prepare a grounded knowledge brief

Use OpenAI Dots to build a separate read-only Hjarni assistant with Agent200. Ground the knowledge brief in returned source data.

On this page
  1. Overview
  2. Before you start
  3. Setup steps
  4. Test your connection
  5. Instructions for AI agents
  6. Hjarni tools
  7. How it works
  8. Troubleshooting
  9. FAQ

Overview

Build a separate knowledge brief application with Agent200. Use the runtime’s real schemas and preserve the project context. This is an architecture guide, not a native installation in OpenAI Dots.

Start with one identified note. Preserve the note title, body, container and source identity actually returned; report missing data and keep the workflow read-only.

Provider reference: Hjarni MCP reference.

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

Connector
Hjarni
Works with
OpenAI Dots · Your own agent code
Authentication
Your Agent200 API key
Tools
6 tools
Model in examples
openai/gpt-5.6-sol

Before you start

  • An Agent200 API key. Create one on the API keys page of the dashboard.
  • Hjarni enabled for your project. In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
  • A model for your agent. The examples use openai/gpt-5.6-sol, through the same Agent200 API key.

Connect Hjarni to OpenAI Dots

  1. 1

    Step 1: Create your Agent200 API key

    Create a key on the API keys page and store it securely.

    .env
    Conceptual example
    Store the Agent200 API key as an environment variable
    # Keep the key out of your code, prompts and chats.
    export AGENT200_API_KEY="paste-your-key-here"
  2. 2

    Step 2: Inspect the real tool definitions

    Confirm the actual Hjarni read operations and input schemas in your runtime.

  3. 3

    Step 3: Enable the Hjarni tools

    Use the project’s Agent200 API key and inspect the Hjarni read tools advertised by the runtime. No separate Hjarni key is needed through Agent200.

  4. 4

    Step 4: Build and test the read-only answer

    Prepare the knowledge brief only from returned source data. The code example illustrates a sequence, not an SDK installation contract.

    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);

Test your connection

Run one request to check everything is wired up.

Ask

Search for the Hjarni note I name, read that note, and prepare a concise knowledge brief from its returned body. Name the note and folder or space when returned. State access gaps and do not create or change notes.

What should come back

  • The selected note and its returned content are identified.
  • Only notes returned by the enabled Hjarni tools are used.
  • Access gaps and missing context are explicit; no note is changed.

Check project tool enablement, selected note ID and result scope. Do not infer that an unreturned note does not exist.

Get your API key

Create a key in the Agent200 dashboard. It reaches Hjarni and every other connector enabled for your project.

Read the SDK docs

Instructions for AI agents

Using a coding agent? Paste this brief into it, or give it the address of this page. It lists what to do, in order, to connect Hjarni to OpenAI Dots.

Agent brief
Goal: connect Hjarni to OpenAI Dots with Agent200.
Guide: https://www.agent200.com/connectors/hjarni/framework/openai-dots/

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. Make sure Hjarni is enabled for the project in the Agent200 dashboard (Connectors), with the endpoints and scopes the task needs.
3. Add the Agent200 SDK to the project and create a client with that key.
4. Run requests through Agent200 with a model (for example openai/gpt-5.6-sol) and "hjarni" in the tools. The model decides when a Hjarni tool is needed; Agent200 executes the call.
5. Check it works with this request: "Search for the Hjarni note I name, read that note, and prepare a concise knowledge brief from its returned body. Name the note and folder or space when returned. State access gaps and do not create or change notes."
   What should come back:
   - The selected note and its returned content are identified.
   - Only notes returned by the enabled Hjarni tools are used.
   - Access gaps and missing context are explicit; no note is changed.
6. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard, then retry.

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

The whole guide is also available as Markdown, for agents and LLMs: /connectors/hjarni/framework/openai-dots.md

Hjarni tools OpenAI Dots can call

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

How it works

  1. 01

    Your app sends the request

    It calls Agent200 with the model, instructions, the input and the Hjarni tools.

  2. 02

    The model picks a tool

    The model decides whether a Hjarni tool is needed, and with which arguments.

  3. 03

    Agent200 runs the call

    It reaches Hjarni with your Agent200 API key, within the endpoints your project allows, and returns the result to the model.

  4. 04

    Your app gets the result

    Agent200 returns the completed result. Your app decides when the agent runs and what happens next.

Permissions at every level. Your project settings decide which services and endpoints the agent may use.

Troubleshooting

The source cannot be read

Check the project’s Hjarni tool availability, selected note ID and pagination. Treat a missing or refused note as an access or scope result, not as evidence that it never existed.

FAQ

How do I verify this result?

Compare the named note and returned note title, body, container and source identity actually returned with the source. Treat missing information as missing, not as a fact.

Is this a native product integration?

This describes a separate application built with Agent200 and OpenAI Dots; it does not install a connector into the OpenAI Dots app.

Use Hjarni with another framework

200 OK

Hjarni, connected to OpenAI Dots.
One SDK. One API key.

Agent200 handles the OAuth, the tokens and every tool call. You keep your agent, your model and your code.

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)