Taktikal Is Taktikal Core API

Setup

Wiring the Taktikal Core API by hand means setting up HTTP basic auth with an API key scoped to the right resource and threading sequence and signee keys through nested signing routes yourself. Through Jentic you install once, import the Taktikal Core API from the API Directory, store the basic credential once, and your agent calls it.

Permission scoping

Taktikal puts the sequence key in the URL path (/signing/sequential/{SequenceKey}/...), so a rule can pin your agent to one signing sequence: it can read that sequence's signees and nothing else. You choose the operations it may call, so adding a signee or updating one is not included unless you add it.

Credential isolation

Your Taktikal basic credential 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.

Intent-based discovery

Agents search Jentic by intent such as 'read the signing activity log' or 'add a signee to a sequence', and Jentic returns the matching Taktikal operation with its input schema so the agent calls the right endpoint without browsing the reference docs.