Install Jentic One Beta

Connect the VivifyScrum API to your agent

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

Add a new item/task

Edit an item

Delete an item

Get item by code or ID

List sprints

GET STARTED

Start building with VivifyScrum API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use VivifyScrum API for, with concrete tasks.

★ Productivity Operations

Use the VivifyScrum API to perform productivity operations programmatically. The API provides 8 endpoints covering core functionality including add a new item/task, edit an item, delete an item.

Call POST /task to add a new item/task

Automated Board Export Management

Automate board export operations by combining multiple VivifyScrum API endpoints. Agents can edit an item and then delete an item in a single workflow.

Call PUT /task to edit an item, then verify the result

AI Agent Integration via Jentic

AI agents discover and call VivifyScrum API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.

Search Jentic for 'add a new item/task', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

8 endpoints — project management and scrum tool api.

METHOD

PATH

DESCRIPTION

POST

/task

Add a new item/task

PUT

/task

Edit an item

DELETE

/task

Delete an item

GET

/task/{taskCode}

Get item by code or ID

GET

/sprints

List sprints

GET

/sprints/{sprintId}/tasks

Get sprint items

GET

/sprints/{sprintId}/export

Export sprint data

GET

/board-export

Export board (once per 24h)

POST

/task

Add a new item/task

PUT

/task

Edit an item

DELETE

/task

Delete an item

GET

/task/{taskCode}

Get item by code or ID

GET

/sprints

List sprints

GET

/sprints/{sprintId}/tasks

Get sprint items

GET

/sprints/{sprintId}/export

Export sprint data

GET

/board-export

Export board (once per 24h)

Why Jentic?

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

Setup

Wiring VivifyScrum by hand means handling its bearer token auth against www.vivifyscrum.com and managing the task and sprint calls yourself. Through Jentic you install once, import VivifyScrum from the API Directory, store the token once, and your agent calls it.

Permission scoping

VivifyScrum puts the sprint id in the URL path (/sprints/{sprintId}/tasks), so a rule can pin your agent to reading and exporting one sprint. You choose the operations it may call, so task deletion on /task is not included unless you add it.

Credential isolation

Your VivifyScrum 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.

Intent-based discovery

Agents search Jentic by intent such as 'add a new task' or 'list tasks in a sprint', and Jentic returns the matching VivifyScrum operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using VivifyScrum API through Jentic.

What authentication does the VivifyScrum API use?

The VivifyScrum API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

Can I add a new item/task with the VivifyScrum API?

Yes. Use the POST /task endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the VivifyScrum API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I add a new item/task through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'add a new item/task'. Jentic returns the matching VivifyScrum API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the VivifyScrum API have?

The VivifyScrum API exposes 8 endpoints covering board export, sprints, task operations.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which VivifyScrum operations and credentials your agent may use. Because the sprint id sits in the URL path, such as GET /sprints/{sprintId}/tasks and GET /sprints/{sprintId}/export, you can pin the agent to reading and exporting a single sprint. You also choose which operations it can call, so a destructive request like DELETE /task is off limits unless you explicitly add it.

VivifyScrum API

Name: VivifyScrum API
Brand: VivifyScrum API
Availability: InStock

Official vendor OpenAPI document · agent-readyProductivityTask Managementbearer8 EndpointsREST

For Agents

Programmatically add a new item/task, edit an item. Covers 8 operations with bearer authentication.

Use for: I need to add a new item/task, I want to edit an item, Search for an item, Find all item by code or id

Not supported: Does not handle payments, communications, or crm - use for productivity only.

Project management and Scrum tool API. Manage tasks/items, sprints, and boards. The API exposes 8 endpoints secured with bearer authentication.

Jentic One on Github View OpenAPI Document

Connect the VivifyScrum API to your agent

Capabilities

Start building with VivifyScrum API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

VivifyScrum API