Install Jentic One Beta

Connect the Planka API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Planka 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%2Fplanka.app%2Fplanka" | 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%2Fplanka.app%2Fplanka" | 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 Planka API.

Logout (delete token)

Create a project

List all projects

Get project details

GET STARTED

Start building with Planka API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Planka API for, with concrete tasks.

★ Productivity Operations

Use the Planka API to perform productivity operations programmatically. The API provides 45 endpoints covering core functionality including login and get access token, logout (delete token), create a project.

Call POST /api/access-tokens to login and get access token

Automated Auth Management

Automate auth operations by combining multiple Planka API endpoints. Agents can logout (delete token) and then create a project in a single workflow.

Call DELETE /api/access-tokens to logout (delete token), then verify the result

AI Agent Integration via Jentic

AI agents discover and call Planka 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 bearer tokens manually.

Search Jentic for 'login and get access token', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

45 endpoints — planka is an open-source trello-like kanban board.

METHOD

PATH

DESCRIPTION

POST

/api/access-tokens

DELETE

/api/access-tokens

Logout (delete token)

POST

/api/projects

Create a project

GET

/api/projects

List all projects

GET

/api/projects/{projectId}

Get project details

PATCH

/api/projects/{projectId}

Update a project

DELETE

/api/projects/{projectId}

Delete a project

POST

/api/projects/{projectId}/managers

Add project manager

POST

/api/access-tokens

DELETE

/api/access-tokens

Logout (delete token)

POST

/api/projects

Create a project

GET

/api/projects

List all projects

GET

/api/projects/{projectId}

Get project details

PATCH

/api/projects/{projectId}

Update a project

DELETE

/api/projects/{projectId}

Delete a project

POST

/api/projects/{projectId}/managers

Add project manager

Why Jentic?

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

Setup

Wiring Planka by hand means learning its bearer access-token auth, setting the host for your own Planka instance, and hand-building requests across its project and access-token endpoints yourself. Through Jentic you install once, import Planka from the API Directory, store the token once, and your agent calls it.

Permission scoping

Planka puts the project id in the URL path (/api/projects/{projectId}), so a rule can pin your agent to one project: it reads and updates that project and manages its members and nothing else. You choose the operations it may call, so destructive ones like deleting a project are not included unless you add them.

Credential isolation

Your Planka token 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 'log in and get an access token' or 'create a project', and Jentic returns the matching Planka operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Planka API through Jentic.

What authentication does the Planka API use?

The Planka API uses a Bearer token in the Authorization header. 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 login and get access token with the Planka API?

Yes. Use the POST /api/access-tokens endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Planka 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 login and get access token through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'login and get access token'. Jentic returns the matching Planka API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Planka API have?

The Planka API exposes 45 endpoints covering auth, projects, boards operations.

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

Yes. Because you run Jentic One yourself, you decide which Planka operations and credentials the agent may use, and your own rules govern every call. Since Planka carries the project id in the URL path (/api/projects/{projectId}), you can pin the agent to a single project so it only reads and updates that project and manages its members. You choose the operations it may call, so destructive ones such as deleting a project stay off limits unless you explicitly add them.

Planka App Planka API

Name: Planka API
Brand: Planka API
Availability: InStock

AI ReadinessAI-Aware (B)65/100

See full scorecard

Official vendor OpenAPI document · agent-readyProductivityTask Managementbearer45 EndpointsREST

For Agents

Programmatically login and get access token, logout (delete token). Covers 45 operations with bearer authentication.

Use for: I need to login and get access token, I want to logout (delete token), Search for a project, Find all all projects

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

Planka is an open-source Trello-like kanban board. The API provides management of projects, boards, lists, cards, labels, tasks, comments, attachments, and users. The API exposes 45 endpoints secured with bearer authentication.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

97%

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

60%

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: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

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

35%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

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

61%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

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: CSignals: 1

57%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Planka API to your agent

Capabilities

Start building with Planka API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Planka App Planka API

Jentic AI Readiness Score

Planka 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