Install Jentic One Beta

Connect the Planzer.io API to your agent

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

Create a task with a title, notes, planned date, deadline, estimate_minutes, priority, project_id, and tag_id, or drop it into the inbox by leaving the date out

List tasks newest first, filtered by open or completed status and by text in the title, with up to 100 per page

Mark a task complete by its taskId and read back its completed_at timestamp

Look up the active projects and tags to file new tasks under the right ones

GET STARTED

Start building with Planzer.io API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Planzer.io API for, with concrete tasks.

★ Agent-Driven Task Capture via Jentic

An AI assistant that reads email or meeting notes turns action items into Planzer tasks. Through Jentic it looks up the right project and tag, creates each task with a title, deadline, priority, and estimate, and leaves undated items in the inbox for later planning, so action items land in the planner instead of a chat log.

List projects to find the id of 'Client Work', then create a task titled 'Send Q3 report to Acme' with deadline 2026-11-20, priority high, estimate_minutes 45, and that project_id

Daily Review of Open Work

Someone planning their day asks for what is still open. The listTasks operation returns tasks newest first with status set to open, and the search parameter narrows by title text, so an assistant can surface everything mentioning a client or project before the day starts and complete finished items in the same session.

List open tasks with search 'Acme' and limit 50, then complete the task titled 'Book kickoff call' with completeTask

Syncing Completed Tasks to Other Tools

Teams that log finished work elsewhere subscribe a webhook to task.completed. Planzer posts to the target_url whenever a task is completed, so a time tracker, CRM note, or status report can be updated without polling, and the subscription is removed with a single unsubscribe call when it is no longer needed.

Create a webhook for event task.completed with target_url https://hooks.example.com/planzer, then confirm it by completing a test task

Key Endpoints

9 endpoints — the planzer.

METHOD

PATH

DESCRIPTION

POST

/tasks

Create a task

GET

/tasks

List and search tasks

GET

/tasks/{taskId}

Get a task

POST

/tasks/{taskId}/complete

Complete a task

GET

/projects

List active projects

POST

/webhooks

Subscribe to a task event

DELETE

/webhooks/{webhookId}

Unsubscribe a webhook

POST

/tasks

Create a task

GET

/tasks

List and search tasks

GET

/tasks/{taskId}

Get a task

POST

/tasks/{taskId}/complete

Complete a task

GET

/projects

List active projects

POST

/webhooks

Subscribe to a task event

DELETE

/webhooks/{webhookId}

Unsubscribe a webhook

Why Jentic?

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

Setup

Wiring Planzer.io by hand means creating a personal pk_ key, sending it as a bearer token, handling the 429 Retry-After limit, and running a receiver for webhook events. Through Jentic you install once, import Planzer.io from the API Directory, store the key once, and your agent manages tasks.

Permission scoping

Planzer.io puts the task id in the URL path (/tasks/{taskId}/complete), so a rule can pin your agent to completing one task. You choose the operations it may call, so webhook creation and deletion are not included unless you add them.

Credential isolation

Your Planzer.io 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 'add a task to my planner' or 'complete a task', and Jentic returns the matching Planzer.io operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Planzer.io API through Jentic.

What authentication does the Planzer.io API use?

The Planzer.io API uses bearer authentication per its OpenAPI spec: create a personal API key in Planzer under Settings, Integrations, API keys and send it as Authorization: Bearer pk_... A key gives access to the tasks of the account that created it. Through Jentic the key is stored encrypted on your own instance and injected at call time.

Is there a Planzer.io MCP server?

You don't need an MCP server to give your agent Planzer.io. Jentic connects it directly from the API Directory: import Planzer.io, store your API key once, and your agent can create and complete tasks straight away. Operations are discovered on demand, so no extra server's tool definitions sit in your agent's context.

Can I limit what my agent is allowed to do with the Planzer.io API?

Yes. Write a rule that allows only listTasks, getTask, and createTask, so the agent can read and add tasks but cannot complete them or register and delete webhooks, and every call it makes is logged.

What are the rate limits for the Planzer.io API?

Per the Planzer.io OpenAPI spec, requests are limited to 120 per minute per API key, or per IP address for requests without a valid key. Over the limit the API returns 429 with a Retry-After header.

How does the Planzer.io API interpret task dates?

The date field takes YYYY-MM-DD, the word today, or an ISO date-time, and is read as a day in the account's time zone, which you can check with the getMe operation. Leaving the date out puts the task in the inbox. The deadline field accepts YYYY-MM-DD or an ISO date-time in the same way.

How do I create a task with the Planzer.io API through Jentic?

Search Jentic for an intent like 'add a task to my planner', import Planzer.io, and store your API key once. Your agent then calls createTask at /tasks with a title and optional date, deadline, priority, and project_id. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Planzer.io API

AI ReadinessAI-Aware (B)64/100

See full scorecard

Official vendor OpenAPI document · agent-readyProductivityTask Managementbearer9 EndpointsREST

For Agents

Create, search, and complete tasks in Planzer.io with dates, deadlines, estimates, priorities, projects, and tags, and subscribe a webhook to task.created or task.completed events.

Use for: I need to add a task to my Planzer inbox, Create a high priority task due on Friday with a 30 minute estimate, Find all open tasks with 'invoice' in the title, Mark this Planzer task as completed

Not supported: Does not handle calendar events, team assignment, or time tracking. Use for creating, searching, and completing personal Planzer tasks only.

The Planzer.io API reads and creates tasks in a Planzer account and notifies your endpoint when tasks are created or completed. A new task takes a title plus optional notes, a planned date, a deadline, an estimate in minutes, a priority from none to urgent, and a project and tag; leaving the date out puts it in the inbox. Tasks can be listed newest first with status, sort, and title search filters, fetched one at a time, and marked complete. The same API backs Planzer's Zapier and Make integrations, and each personal API key reaches only the tasks of the account that created it.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

99%

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

100%

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

29%

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.

50%

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

60%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Planzer.io API to your agent

Capabilities

Start building with Planzer.io API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Planzer.io API

Jentic AI Readiness Score

Planzer.io 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