What authentication does the agentda API use?

Per its OpenAPI spec, agentda uses an access token sent in the Authorization header as Bearer followed by the token, and the raw token without the Bearer prefix is also accepted. The spec applies it to every operation. Through Jentic, the token is stored encrypted by your own Jentic One instance and injected at call time.

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

Yes. For example, write a rule that allows only GET /api/v1/knowledge/search, GET /api/v1/topics/{ref}/documents/{id}, and POST /api/v1/topics/{ref}/documents under topic T-3. Your agent can then search, read, and add notes in that one topic, but it cannot change members, archive topics, or delete documents, and every call it makes is logged.

What are the rate limits for the agentda API?

The OpenAPI spec states a limit of 120 documents per hour per user for saving new documents with POST /api/v1/topics/{ref}/documents. It does not state a general request limit for the other operations.

How do I save a note to agentda through Jentic?

Search Jentic for 'save a note to the team knowledge base', load the createTopicDocument operation, and call POST /api/v1/topics/{ref}/documents with the topic ref, a title, and content_md. Writing needs topic admin or writer access. To run it on your own infrastructure, install Jentic One from its GitHub repo.

How do I refer to a topic in the agentda API?

The ref path parameter accepts the topic number such as T-3, the topic's unique name, or its UUID. Unknown topics, and topics the user cannot see, return 404, since visibility requires membership or a workspace-visible topic.

Can agentda search find documents by meaning, not just keywords?

Yes. GET /api/v1/knowledge/search runs hybrid full-text and semantic search across all topics visible to the user and falls back to full-text when semantic search is unavailable. The q parameter needs at least 2 characters, and results are snippets, so fetch the full document with the document endpoint.