I see through your request that you asked for a private mirror.
As mirrormanager will not be able to validate your mirror (crawling it) I guess you know that it will have to be marked as "always up2date" and so that you'll have to verify at your side the content.
Also : you are probably already syncing from a third-party mirror for stream content too ? (if that's the case, that would explain why you haven't mentioned any public ipv4/ipv6 address from which you'd pull content from)
Can you just confirm that it summarizes your request ?

Private mirrors should use report_mirror. "always up2date" is an option only MirrorManager admins can set. Which we did for other private mirrors before. report_mirror is the expected way to go. I remember one private mirror where we set "always up2date" as that mirror was basically a caching proxy type of setup.

@adrian thanks for the clarifications. Let's wait for feedback for confirmation from their side, and I'll then just add the CentOS category with the listed URLs above

Correct on your assumptions.

We're currently pulling the content from a local third party mirror, so no IP's listed for mirroring. If you prefer that we pull direct I can provide the relevant address for that.
Our existing mirrors of Fedora/EPEL content use quick-fedora-mirror to report status as part of the sync, but we also use report_mirror for other content so can use that for this mirror as well.

@ibmswguklnx : the CentOS category was already added on your host, so nothing to do at our side anymore. If you use report_mirror for centos content, it should show up in metalinks for your networks