Jentic publishes the only available OpenAPI specification for Microsoft Teams Events API, keeping it validated and agent-ready. The API is a curated slice of Microsoft Graph covering Microsoft Teams - team and channel management, channel messages, members, installed apps, tabs, calls, online meetings, schedule shifts, group calendar events, and activity feed notifications. It uses OAuth 2.0 with Microsoft Entra ID (formerly Azure AD) and is consumed via 35 endpoints under the v1.0 Graph host.
35 endpointsJentic publishes the only available OpenAPI specification for Microsoft To Do API (Graph), keeping it validated and agent-ready. The Microsoft To Do API exposes task management capabilities via Microsoft Graph, letting applications create and organise task lists, add tasks with due dates and reminders, attach checklist items, and link external resources. It uses OAuth 2.0 bearer tokens scoped to the signed-in user's mailbox and supports the same task data that surfaces in Microsoft To Do, Outlook Tasks, and Planner integration scenarios. The 14 endpoints cover full lifecycle operations on lists, tasks, checklist items, and linked resources.
14 endpointsStep 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.