What authentication does the Hjarni REST API use?

The Hjarni REST API authenticates with a bearer token in the Authorization header, per its OpenAPI spec, and GET /me returns the account and token for a given key. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at call time, so it never enters the agent's prompt or logs.

Can I search and update notes with the Hjarni REST API?

Yes. GET /search finds notes by keyword, GET /notes/{id} returns one note's full Markdown, and PATCH /notes/{id} updates it in place. List responses page with page and per_page and report totals in the X-Total-Count, X-Page, and X-Per-Page headers.

What are the rate limits for the Hjarni REST API?

The Hjarni spec documents a limit of 100 requests per minute per account across all of its tokens, and going over returns 429 with a Retry-After header. Back off for the number of seconds the Retry-After header indicates.

How do I search notes through Jentic?

Search Jentic with the query 'search notes', load the schema for GET /search, and execute it with your keyword, then read matches with GET /notes/{id}. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Can I limit what my agent is allowed to do with the Hjarni REST API?

Yes. Write a rule that allows only GET /search, GET /notes, and GET /notes/{id}, so the agent can find and read notes but cannot create, move, or trash them, and every call it makes is logged. Because note ids live in the URL path, you can even confine a read to a single note.