https://docs.avohq.io/4.0/rest-api/ - @lemon-wall-20836 We're building our own internal CLI tool with the goal of automatic some of the common internal business flow. Most of them already exist in Avo (like getting a resource, running an action on this resource), so your Api wrapper around avo is pretty much exactly what we need. Instead of building it ourselves, we were hoping to buy the add on. Only tricky bit I see is that the API wrapper has been created only with avo 4 in mind from what I could tell. What do you think our options are?

Thread automatically created by Martin Tomov in #1138182212655788054

Hi @fresh-thailand-89388 What Avo version are you currently using?

We're on latest released V3

At this point, the Avo API is in the alpha stage and works only with Avo 4

I see, thank you! I guess best course of action is to wait for V4 to be out and official before trying out the API one. Meanwhile, we'll build an internal wrapper? And can I ask there's a plan to have API around actions as well?

> And can I ask there's a plan to have API around actions as well? Didn't thought about it deeply, what is the use case?

well, the same actions that people click on to perform tasks - we want to expose them for to an internally built CLI .. then use an LLM to work with the CLI to perform those actions much quicker

Souds like a job for an avo mcp

short answer si "yes". we have thought about that

💡

use the API wrapper to bridge the REST call to the Avo action

perfect, thank you!, yeah mcp now is the easy part, so long as the api exists. Thank you!