canonical: https://jentic.com/apis/klingo.app/klingo-ferramentas # Klingo App Klingo API Ferramentas The Klingo Ferramentas API creates tasks inside Klingo's clinic management system from an external caller. It exposes a single task-creation endpoint so another system or an agent can register follow-up items, action points, and work requests directly into Klingo's workflow. Access is controlled by an application token sent in a request header. ## For AI agents Create tasks in Klingo's clinic management system from an external caller or AI agent through a single task-creation endpoint. ## Scope Does not schedule appointments, send messages, or manage billing. Use for creating Klingo tasks only. ## Capabilities - Create a new task in Klingo from an external caller or agent - Register follow-up and action items as Klingo tasks for clinic staff - Push task records into Klingo's workflow from your own system ## Use cases ### Create Klingo tasks from an AI agent An AI agent integration created through Jentic needs to hand work to clinic staff. The Klingo Ferramentas API lets the agent create a task directly in Klingo's workflow with a single call, so a follow-up detected elsewhere becomes an actionable item for the team without manual re-entry. Example prompt: Create a task in Klingo describing a patient follow-up and confirm it was registered ### Turn external events into clinic tasks A reminder or alert raised in another system should become a task the clinic can act on. The Klingo Ferramentas API accepts task creation from an outside caller, so an automation can translate an incoming event into a Klingo work item for staff to pick up. Example prompt: Create a Klingo task from an incoming scheduling alert and verify the response ### Register action items from a review After a case review, several action items need tracking. The Klingo Ferramentas API lets a caller create one task per action point so each is captured in Klingo rather than left in notes, keeping the clinic's workflow the single source of outstanding work. Example prompt: Create a Klingo task for each action item from a case review ## Key resources - **Tasks** — Create tasks in Klingo's clinic management workflow from an external caller ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 67 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 100 / 100 - Developer Experience & Jentic Compatibility: 78 / 100 - AI-Readiness & Agent Experience: 54 / 100 - Agent Usability: 94 / 100 - Security: 50 / 100 - AI Discoverability: 50 / 100 - **View full report:** https://jentic.com/apis/klingo.app/klingo-ferramentas/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring Klingo Ferramentas by hand means setting the X-APP-TOKEN header on every call and matching the right base path for the tools service. Through Jentic you install once, import Klingo Ferramentas from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** The task details travel in the request body, so rules bound which operations your agent may call, not which task. You allow the task-creation operation and nothing else, so the agent can open tasks without reaching any other Klingo capability. - **Credential handling:** Your Klingo application 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. - **Discovery method:** Agents search Jentic by intent such as 'create a task in Klingo', and Jentic returns the matching Klingo Ferramentas operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Asana** — Asana is a general-purpose work and task management platform; Klingo Ferramentas creates tasks inside Klingo's clinic system. - **ClickUp** — ClickUp manages tasks, docs, and goals across teams; Klingo Ferramentas is scoped to Klingo clinic task intake. - **Trello** — Trello gives tasks a visual board; pair it with Klingo Ferramentas to mirror created tasks onto a Kanban view. ## FAQ ### What authentication does the Klingo Ferramentas API use? The Klingo Ferramentas API authenticates with an application key sent in the X-APP-TOKEN request header, per its OpenAPI spec. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at call time, so it never reaches the agent's prompt or logs. ### Can I create a task with the Klingo Ferramentas API? Yes. The API exposes a task-creation endpoint that registers a new task in Klingo's clinic workflow from an external caller, so an agent can hand a detected follow-up to clinic staff with one call. ### What data does the Klingo Ferramentas API return when a task is created? The task-creation endpoint accepts the task payload and returns Klingo's confirmation that the task was registered in the workflow. Use the response to verify the task landed before reporting success to the user. ### How do I create a Klingo task through Jentic? Install Jentic One on your own infrastructure with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, then import the Klingo Ferramentas API from the API Directory and search for 'create a task in Klingo'. Store the application token once and your agent can create tasks. To run it on your own infrastructure, install Jentic One from its GitHub repo. ### Is there a Klingo Ferramentas MCP server? You don't need an MCP server to give your agent the Klingo Ferramentas API. Jentic connects it directly from the API Directory: import it, store your token once, and your agent calls it, with the operation discovered on demand instead of loaded into the agent's context. ### Can I limit what my agent is allowed to do with the Klingo Ferramentas API? Yes. The task details travel in the request body, so a rule bounds which operations the agent may call rather than which task. Allow only the task-creation operation and the agent can open tasks and nothing else, and every action it takes is recorded in an audit log.