Before Core, when the controllers for MVC and Web API were separate, it was easy to target a a global action at one framework or the other. Now with mvcOptions.Filters.Add<T>(); it'll apply across your MVC view rendering actions and you're API-only actions.
I can see roughly that when you use [ApiController] (docs), you're opted in to several conventions/behaviours, but it's not super clear how/if I could add to that convention easily. Potentially I need to create my own additional ApiBehaviorApplicationModelProvider, like the one here? I'm looking for something a little simpler, like mvcOptions.ApiConvention.Filters.Add(x).
Another approach is to have all my API controllers inherit my own ApiControllerBase and annotate that, but I'd prefer to extend the convention if possible.
It'd also be nice to go the other way without having to have a MvcControllerBase either that's for views.