I'm thinking of how Google organizes API REST response equivalent information pertaining to a resource that you are looking at. For example, where you can access various resources via the API. So if I look at an image, for example, it shows me the URL of that image, etc.

Great product, but for a new user, the endpoints you provide are kinda hard to digest from documentation alone, so I've been spending too much time trying to troubleshoot. Working backwards, and having the specific information that I need to GET artifacts, for example, is a more intuitive way to learn your API, imo.

CCI-I-972