h3. Problem Live APIs can live anywhere and have hard-coded requirements. For example, pulp_ansible expects to server various urls also rooted at /api/v3/ because the Galaxy API works like that and it's also at version 3. I don't think any of the core provided urls formally collide with Galaxy urls. The same problem can occur with the /content/ app. h3. Solution Pulp could minimize these types of issues by rooting everything under <code>/pulp/</code> so making the Pulp API would move to <code>/pulp/api/v3/</code> and content to <code>/pulp/content/</code>. even more unique like <code>/pulpapi/v3/</code>.