Then again I don't I tend to think in terms of endpoints and instead focus more on Hypermedia aspects of REST API's and link relations.
For example hinting about a resource profile for a link relation or indicating a resource own profile on the self link, gives the necessary information for clients to know what to expect.
Basically a profile is something you can append to almost any generic media type or as a separate hint, either with an actual link withe the relation "profile" on the resource it self or some other channel before even requesting the resource, similar to the "profile" property on links in hal+json.
But if there are no common capabilities or properties between the resources, and you don't need to return them in a mixed collection, then it might actually be better to separate them. And if the resources are not backed by the same set of unique ID's it might get a bit cumbersome to encode the type as part of the item ID's.