Install Jentic One Beta

Connect the Plane API to your agent

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

Create projects and work items in a workspace

Move work items through project workflow states

Group work into cycles and modules

Label and categorize work items

List workspace members and project states

GET STARTED

Start building with Plane API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Plane API for, with concrete tasks.

★ AI Project Management Agent

An AI agent connected to Plane through Jentic can file work items from incoming requests, assign them to a cycle, and move them through workflow states as work progresses. Because Plane is open-source and self-hostable, teams keep their project data on their own infrastructure while the agent drives the board.

Create a work item in a project, add it to the current cycle, and set its workflow state to in-progress

Issue Tracking

Track issues as work items that move through a project's workflow states. The Plane API creates work items, updates their fields, and applies labels so a backlog stays organized and queryable.

Create a work item, apply a bug label, and move it to the triage state

Cycle and Module Planning

Plan work into cycles and modules to organize sprints and feature groupings. Plane lets an agent create cycles and modules in a project and list the states work items can occupy.

Create a new cycle for a project and list its workflow states

Key Endpoints

18 endpoints — the plane api manages projects and work items for teams using the open-source project management tool.

METHOD

PATH

DESCRIPTION

GET

/workspaces/{workspace_slug}/projects

List projects in a workspace

POST

/workspaces/{workspace_slug}/projects

Create a project

GET

/workspaces/{workspace_slug}/projects/{project_id}/work-items

List work items in a project

POST

/workspaces/{workspace_slug}/projects/{project_id}/work-items

Create a work item

PATCH

/workspaces/{workspace_slug}/projects/{project_id}/work-items/{work_item_id}

Update a work item

POST

/workspaces/{workspace_slug}/projects/{project_id}/cycles

Create a cycle

GET

/workspaces/{workspace_slug}/projects

List projects in a workspace

POST

/workspaces/{workspace_slug}/projects

Create a project

GET

/workspaces/{workspace_slug}/projects/{project_id}/work-items

List work items in a project

POST

/workspaces/{workspace_slug}/projects/{project_id}/work-items

Create a work item

PATCH

/workspaces/{workspace_slug}/projects/{project_id}/work-items/{work_item_id}

Update a work item

POST

/workspaces/{workspace_slug}/projects/{project_id}/cycles

Create a cycle

Why Jentic?

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

Setup

Wiring Plane by hand means sending its API key in a custom header and learning the workspace, project, and work-item path structure yourself. Through Jentic you install once, import Plane from the API Directory, store the key once, and your agent calls it.

Permission scoping

Plane puts the project id in the URL path, so a rule can pin your agent to one project: it can create and update work items there and nothing else. You choose the operations it may call, so project deletion is not included unless you add it.

Credential isolation

Your Plane API key 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 'create a work item' or 'list projects', and Jentic returns the matching Plane operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Plane API through Jentic.

Is there a Plane MCP server?

You don't need an MCP server to give your agent the Plane API. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent can create and update work items. Operations are discovered on demand, so your agent's context stays lean.

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

Yes. Plane puts the project id in the URL path, so a rule can pin your agent to one project and allow only work-item creation and updates there. The agent cannot delete the project or touch other projects unless you add those operations, and every call is logged.

What authentication does the Plane API use?

The Plane API authenticates with an API key sent in the X-API-Key header per its OpenAPI spec; you generate the key from Personal Access Tokens in your profile settings. With Jentic, the key is stored encrypted by your own Jentic One instance and injected at call time.

Can I create a work item with the Plane API?

Yes. The work-items endpoint creates an item in a project, and a related endpoint updates its fields and state. You can also add the item to a cycle or module and apply labels to categorize it.

What are the rate limits for the Plane API?

The OpenAPI spec does not specify rate limits. Check the Plane developer documentation at https://developers.plane.so for current limits before running bulk work-item operations.

How do I create a work item with the Plane API through Jentic?

Import the Plane API from the Jentic API Directory, store your API key once, and have your agent search by intent such as 'create a work item'. Jentic returns the create operation with its input schema, and your agent passes the workspace and project. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Plane So Plane API

AI ReadinessAI-Aware (B-)61/100

See full scorecard

Official vendor OpenAPI document · agent-readyDeveloper ToolsProject ManagementapiKey18 EndpointsREST

For Agents

Create and update projects, work items, cycles, modules, labels, and workflow states in a Plane workspace. Programmatic access to an open-source Jira and Linear alternative.

Use for: Create a new work item in a project, List all projects in a workspace, Move a work item to a different state, Start a new cycle for a project

Not supported: Does not handle source code hosting, CI/CD, or time tracking. Use for project and work item management only.

The Plane API manages projects and work items for teams using the open-source project management tool. It creates and updates projects, work items, cycles, modules, labels, and workflow states within a workspace. Plane is positioned as a Jira and Linear alternative, giving agents programmatic control over an issue tracker that teams can self-host.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

98%

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

75%

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: C+Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

35%

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: DSignals: 4

11%

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.

67%

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: C-Signals: 1

50%

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

62%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Plane API to your agent

Capabilities

Start building with Plane API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Plane So Plane API

Jentic AI Readiness Score

Plane 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