@YvanDaSilva The management API is meant for end users and provisioning tools to interact with. It will be provided locally by the Incus OS daemon because we don't want to have to manage yet another authenticated HTTPS endpoint. Instead the Incus daemon itself will detect the Incus OS daemon socket and then act as a proxy for that API, effectively exposing it externally and handling authentication for it. As it's a user facing API meant to be incorporated into the Incus API, we're only planning on doing REST.