canonical: https://jentic.com/apis/krozu.com/krozu

# Krozu API

Jentic publishes the only available OpenAPI specification for Krozu API, keeping it validated and agent-ready. The Krozu API exposes three endpoints for the Krozu task and workflow management platform - listing tasks, creating new tasks, and listing workflows - for teams that want to integrate Krozu with internal tools, intake forms, and automation. The spec uses an API key passed in a header for authentication and is intentionally narrow, mirroring Krozu's focus on lightweight task creation rather than full project management.

## For AI 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.

## Scope

Does not handle task updates, comments, attachments, or assignment changes - use for task creation, task listing, and workflow listing only.

## Capabilities

- 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
- Authenticate every request with a single header-based API key tied to a Krozu account
- Pair with downstream automation by reading task IDs returned at creation time

## Use cases

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

Example prompt: 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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

| Method | Path | Description |
| --- | --- | --- |
| GET | `/tasks` | List tasks in the workspace |
| POST | `/tasks` | Create a new task |
| GET | `/workflows` | List configured workflows |

## Key resources

- **Tasks** — List existing tasks and create new ones in the workspace
- **Workflows** — List the workflows configured in the Krozu account

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Asana** — Full-feature task and project management platform with broader CRUD endpoints
- **Trello** — Board-and-card task tool with mature REST API for cards, lists, and labels
- **ClickUp** — Task tracker with extensive views, custom fields, and webhooks
- **monday.com** — Work management platform with GraphQL API for items and boards

## FAQ

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