Install Jentic One Beta

Connect the Taktikal Core API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Taktikal Core API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ftaktikal.is%2Ftaktikal-is" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ftaktikal.is%2Ftaktikal-is" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Taktikal Core API.

Get activity log total for paging support

Authenticate a signee into a signing sequence

Start authentication with e-ID for sequence

Poll authentication completion for sequence

Add a sequential signee

GET STARTED

Start building with Taktikal Core API

Explore with Jentic One

View OpenAPI Document

Automated Activity Management

Automate activity operations by combining multiple Taktikal Core API endpoints. Agents can get activity log and then authenticate a signee into a signing sequence in a single workflow.

Call GET /signing/activity to get activity log, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Taktikal Core API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle basic tokens manually.

Search Jentic for 'get activity log total for paging support', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

66 endpoints — taktikal is a digital signing and onboarding platform providing e-signing, sequential signing, authentication, compliance, document management, and webhook capabilities.

METHOD

PATH

DESCRIPTION

GET

/signing/activity/total

Get activity log total for paging support

GET

/signing/activity

Get activity log

POST

/signing/sequential/{SequenceKey}

Authenticate a signee into a signing sequence

POST

/signing/sequential/{SequenceKey}/auth

Start authentication with e-ID for sequence

POST

/signing/sequential/{SequenceKey}/auth/poll

Poll authentication completion for sequence

POST

/signing/sequential/{SequenceKey}/signee

Add a sequential signee

GET

/signing/sequential/{SequenceKey}/signee/{SequentialSigneeKey}

Get sequential signing by signee key

PUT

/signing/sequential/{SequenceKey}/signee/{SequentialSigneeKey}

Update a sequential signee

GET

/signing/activity/total

Get activity log total for paging support

GET

/signing/activity

Get activity log

POST

/signing/sequential/{SequenceKey}

Authenticate a signee into a signing sequence

POST

/signing/sequential/{SequenceKey}/auth

Start authentication with e-ID for sequence

POST

/signing/sequential/{SequenceKey}/auth/poll

Poll authentication completion for sequence

POST

/signing/sequential/{SequenceKey}/signee

Add a sequential signee

GET

/signing/sequential/{SequenceKey}/signee/{SequentialSigneeKey}

Get sequential signing by signee key

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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.

FAQs

Specific to using Taktikal Core API through Jentic.

What authentication does the Taktikal Core API use?

The Taktikal Core API uses HTTP Basic authentication with username and password. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

Can I get activity log total for paging support with the Taktikal Core API?

Yes. Use the GET /signing/activity/total endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Taktikal Core API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I get activity log total for paging support through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get activity log total for paging support'. Jentic returns the matching Taktikal Core API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Taktikal Core API have?

The Taktikal Core API exposes 66 endpoints covering activity, sequential signing, signing process operations.

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

Yes. Jentic One is self-hosted, so your own rules decide which Taktikal operations and credentials your agent may use. Because Taktikal puts the sequence key in the URL path, such as /signing/sequential/{SequenceKey}, you can pin the agent to a single signing sequence and grant only read access to that sequence's signees. Write operations like adding or updating a signee stay off limits unless you explicitly include them.

Taktikal Is Taktikal Core API

AI ReadinessNon-Ready (F)37/100

See full scorecard

Official vendor OpenAPI document · agent-readyDeveloper ToolsSource Controlbasic66 EndpointsREST

For Agents

Programmatically get activity log total for paging support, get activity log. Covers 66 operations with basic authentication.

Use for: I need to activity log total for paging support, I want to activity log, Search for authenticate a signee into a signing sequence, Find all start authentication with e-id for sequence

Not supported: Does not handle payments, communications, or crm - use for developer tools only.

Taktikal is a digital signing and onboarding platform providing e-signing, sequential signing, authentication, compliance, document management, and webhook capabilities. The API exposes 66 endpoints secured with basic authentication.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

96%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: CSignals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

25%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: D-Signals: 4

12%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

98%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

54%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

92%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1

10%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: B-Signals: 1

60%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Taktikal Core API to your agent

Capabilities

Start building with Taktikal Core API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Taktikal Is Taktikal Core API

Jentic AI Readiness Score

Taktikal Core API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness