Krozu API

Name: Krozu API
Brand: Krozu API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentProductivityTask ManagementapiKey3 EndpointsREST

For Agents

Create and list tasks and inspect workflows on Krozu through a header-based API key, suitable for hooking external intake into a Krozu workspace.

Install Jentic One Beta

Connect the Krozu API to your agent

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

List existing tasks in the connected Krozu workspace for status reporting and triage

Create new tasks programmatically from intake forms, alerts, or upstream workflows

List configured workflows so external systems can route tasks into the right workflow

GET STARTED

Start building with Krozu API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Krozu API for, with concrete tasks.

★ Form-to-task intake automation

An intake form on a marketing site or internal portal posts submissions into Krozu by calling POST /tasks with the form fields mapped onto the task body. Krozu handles assignment, status, and notifications inside the platform. Implementation is a single-call integration that typically takes a few hours including form validation.

Call POST /tasks with title 'Website contact form: pricing question' and body containing the submitter's email and message.

Alert-driven incident creation

A monitoring system creates a Krozu task whenever a service crosses a threshold so on-call engineers see the issue in their normal task queue rather than a separate alerting tool. The team can list workflows once at startup via GET /workflows to confirm the right intake target. The pattern collapses two tools into one for teams already using Krozu as their queue.

On a critical alert from the monitoring system, call POST /tasks with title 'CPU > 90% on web-03' and a body containing the alert payload.

Workspace status reporting

A daily standup tool calls GET /tasks each morning to pull the open task list from Krozu, then renders a digest in chat or email. Filtering, sorting, and grouping happen on the client side because the spec exposes only a flat list endpoint. This is enough for teams whose Krozu workspace covers a single team or workflow.

Call GET /tasks, filter the response client-side for tasks created in the last 24 hours, and post a summary to a Slack channel.

Agent-driven task creation via Jentic

An assistant agent searches Jentic for 'create a task' and is matched to the Krozu POST /tasks operation. The agent supplies the title and body from the user's request and Jentic executes the call with the API key injected from your Jentic One instance. The pattern lets an agent triage a long email thread by spawning concrete Krozu tasks per action item.

Use the Jentic MCP tool krozu_create_task with title 'Follow up with customer about renewal' and body 'Renewal date 2026-07-01, send pricing options'.

Key Endpoints

3 endpoints — jentic publishes the only available openapi specification for krozu api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/tasks

List tasks in the workspace

POST

/tasks

Create a new task

GET

/workflows

List configured workflows

GET

/tasks

List tasks in the workspace

POST

/tasks

Create a new task

GET

/workflows

List configured workflows

Why Jentic?

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

Setup

Wiring the Krozu API by hand means passing your key in the Authorization header on every call to api.krozu.com and mapping the task and workflow request bodies yourself. Through Jentic you install once, import the Krozu API from the API Directory, store the key once, and your agent calls it.

Permission scoping

Krozu's task operations take their targets in the request body rather than the URL path, so scope the agent to the operations it needs, such as listing tasks and workflows. You choose that set, so task creation with POST /tasks is not included unless you add it.

Credential isolation

Your Krozu API key is stored once, encrypted, by your own Jentic One instance and injected into the header 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 task' or 'list workflows', and Jentic returns the matching Krozu operation with its required body schema so the agent constructs a valid payload without browsing the reference docs.

FAQs

Specific to using Krozu API through Jentic.

Why is there no official OpenAPI spec for Krozu API?

Krozu does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Krozu API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Krozu API use?

Krozu uses an API key passed in a request header (apiKey scheme). Jentic stores the key encrypted in your Jentic One instance and injects it on every call so the secret never reaches the agent's prompt.

Can I create tasks programmatically with the Krozu API?

Yes. POST /tasks accepts a task payload and returns the created task. List existing workflows first via GET /workflows so you can route tasks into the right intake when more than one workflow is configured.

What are the rate limits for the Krozu API?

Rate limits are not declared in the OpenAPI spec. Krozu applies per-account ceilings - design retries with exponential backoff and consult Krozu support for the limit on your plan before high-volume integrations.

How do I create a Krozu task from an external alert through Jentic?

Search Jentic for 'create a task', load POST /tasks, and execute it with title and body fields populated from the alert payload. Install the SDK with pip install jentic and Jentic handles the API key injection.

Does the Krozu API expose task updates, comments, or assignment?

Not in this spec. Only listing tasks, creating new tasks, and listing workflows are exposed - updates, comments, attachments, and assignment changes happen in the Krozu UI rather than via the public API.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which of the three Krozu operations your agent can reach: listing tasks with GET /tasks, listing workflows with GET /workflows, and creating tasks with POST /tasks. You can grant only the read operations and leave POST /tasks out, so the agent can report on tasks and workflows without ever creating one unless you add that operation. Because the credential is injected by your instance at call time, an operation the agent has not been given simply is not available to it.

Krozu API

Connect the Krozu API to your agent

Capabilities

Start building with Krozu API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs