I'm probably missing something, so if you could let me know where to look, that'd be nice!
[1] I decompiled it here: https://rinkeby.etherscan.io/bytecode-decompiler?a=0x6b96751...
The contract has no mention of opensea, so they must be reading it from the blockchain somehow - but I guess etherscan doesn't display these tokens in a similar way for some reason. It's all pretty new to me and I definitely don't have a super joined up understanding of it all!
You can use the URI to store base64 encoded image or svg data, and that is super cool; but will be too expensive for larger images, at which point you will link to an IPFS-hosted url.
So OpenSea will just try to call `tokenURI`; if you have implemented the interface correctly, that will succeed, if not, OpenSea will not show a placeholder image.
The only proprietary entity involved in that process seems to be Alchemy. My understanding of them is a bit vague but they seem to just help with making miners aware of the new contract and getting it distributed. But that's just the contract, once it's deployed it's nothing to do with them and the NFTs AFAIK don't pass through them at all.