canonical: https://jentic.com/apis/planero4ka.ru/planero4ka

# Planero4ka Ru Planerka API

The Planerka API powers a kanban board backend, creating cards and moving them between columns with both single and bulk operations. It manages comments on cards, tracks board history with archive and restore, and handles media uploads attached to cards. Registration and login endpoints issue the bearer token that authorizes board access.

## For AI agents

Create and move kanban cards, run bulk move and delete, comment on cards, track board history, and upload media attachments. Registration and login issue the bearer token for board access.

## Scope

Does not handle time tracking, reporting dashboards, or team billing. Use for kanban board and card management only.

## Capabilities

- Create cards and move them between board columns
- Bulk move or delete several cards at once
- Add and edit comments on cards
- Track board history and restore archived comments
- Upload media attachments to cards
- Mark cards as favorites for quick access

## Use cases

### AI Kanban Agent

An AI agent connected to Planerka through Jentic can turn incoming requests into cards, move them across columns as work progresses, and comment on cards to leave a trail. It can also bulk-move a batch of cards when a column is reorganized, keeping the board in sync with the work.

Example prompt: Create a card on the board, add a comment describing the task, and move the card to the in-progress column

### Card Management

Create, move, and comment on kanban cards to keep a board current. Planerka supports single-card moves as well as bulk move and bulk delete, so an agent can reorganize many cards in one request.

Example prompt: Bulk-move a set of cards to the done column and delete the ones marked obsolete

### Board Activity Tracking

Follow what changed on a board by reading its history, and recover context by restoring archived comments. Planerka records board history and keeps an archive of comments an agent can restore when needed.

Example prompt: Retrieve the board history and restore an archived comment on a card

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/api/board` | Get the board |
| POST | `/api/cards` | Create a card |
| POST | `/api/cards/{cardId}/move` | Move a card |
| POST | `/api/cards/{cardId}/comments` | Add a comment to a card |
| GET | `/api/history` | Get the board change history |
| POST | `/api/media/upload` | Upload a media attachment |

## Key resources

- **Board** — The kanban board state, retrieved or replaced as a whole
- **Cards** — Cards created, moved, and bulk-updated across board columns
- **Comments** — Comments on cards, with archive and restore
- **History and Media** — Board change history and media uploads attached to cards

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 42 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 93 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 19 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 39 / 100
- **View full report:** https://jentic.com/apis/planero4ka.ru/planero4ka/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring Planerka by hand means registering for a bearer token, learning its card, move, and bulk endpoints, and handling media uploads yourself. Through Jentic you install once, import Planerka from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Planerka puts the card id in the URL path, so a rule can pin your agent to card creation and moves. You choose the operations it may call, so bulk delete and history clearing are not included unless you add them.
- **Credential handling:** Your Planerka bearer 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.
- **Discovery method:** Agents search Jentic by intent such as 'create a card' or 'move a card', and Jentic returns the matching Planerka operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Trello** — Hosted kanban boards with cards and lists, similar to Planerka's board model.
- **ClickUp** — Broad task and project suite with board views, where Planerka is a focused kanban backend.
- **Notion** — Docs and database workspace, complementing Planerka's kanban card tracking.

## FAQ

### Is there a Planerka MCP server?

You don't need an MCP server to give your agent the Planerka API. Jentic connects it directly from the API Directory: import it, store your bearer token once, and your agent can create and move cards. Operations are discovered on demand, so your agent's context stays lean.

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

Yes. Planerka puts the card id in the URL path, so a rule can limit your agent to card creation and moves while leaving bulk delete and history clearing out unless you add them. Every call Jentic makes on your behalf is logged.

### What authentication does the Planerka API use?

The Planerka API authenticates with a bearer token in the Authorization header per its OpenAPI spec. Registration, login, and health checks need no credential, while board and card operations require the token. With Jentic, the token is stored encrypted by your own Jentic One instance and injected at call time.

### Can I bulk-update cards with the Planerka API?

Yes. The bulk move endpoint relocates several cards in one request and the bulk delete endpoint removes a batch at once. An agent can reorganize a column without issuing a call per card.

### What are the rate limits for the Planerka API?

The OpenAPI spec does not specify rate limits. Check the Planerka website at https://planero4ka.ru for current limits before running bulk card operations.

### How do I create a card with the Planerka API through Jentic?

Import the Planerka API from the Jentic API Directory, store your bearer token once, and have your agent search by intent such as 'create a card'. Jentic returns the create operation with its input schema, and your agent passes the card details. To run it on your own infrastructure, install Jentic One from its GitHub repo.