Half of these do not follow the standard, and that is ordinary rather than unlucky. This page reads a token the way a browser does, in two passes: fetch the tokenURI, then hand image to an <img>, which fetches that as a URL too. Mandalas, Bleeps and Nouns come through both passes untouched, and no repair is made for them: Nouns base64-encodes, and Bleeps writes %2520 precisely so that two decodes land on the space it meant.

Brotchain, ArcadeGlyphs and the Moon do not encode their documents at all, and each contains a # (a fill colour, always). A browser reads that as the start of a fragment, so the very first pass returns a fragment of the JSON and never reaches the artwork. ArcadeGlyphs and the Moon also put the SVG itself in image, where the schema asks for a URI pointing at one.

Those three render above anyway, because the page repairs the envelope and then says so: the repair is named on that token's own page, and ?strict withdraws it and shows what a compliant client gets instead. None of it is the artwork's fault, and none of it is the owner's to suffer.

The Moon is unusual for a different reason: nothing about it was decided at mint. Its contract reads the current block, works out the lunar phase and returns the document to match, with no external resource involved at any point. The caveat there is ours rather than the token's, so it belongs here: Embed.Art caches a document the first time it is asked for, which makes that card the phase at that moment rather than tonight's. A token that rewrites itself is the case a cache does not fit.

Autoglyphs are from 2019, and their tokenURI does not point at a metadata document: it returns the piece itself, a 64 by 64 grid of . O + X | - \ / and # as text/plain. There is no image field anywhere to fetch, because there is no document.

So Embed.Art draws it, and says on the page that it did. The characters are not set in a typeface: each one is the vector primitive the collection's own renderer uses, a slash being the cell's diagonal and O its inscribed circle, which is what makes the strokes join into continuous lines instead of a transcription. Asked with ?strict it reports what a compliant client finds, which is a text file. CryptoPunks gets the same treatment for the same reason, having no tokenURI at all: its art comes from the collection's own onchain renderer, and a punk arrives transparent, so what is behind it is nobody's to invent.

* CryptoKitties is in this group on a technicality, and the asterisk is the honest part. It has no tokenURI either, so there is no document, and what the contract holds is real: a 256-bit gene string, a generation, a birth date, two parents. But the cat itself is not onchain. It is drawn from those genes by CryptoKitties and served from their image host, so unlike everything else in this group, that picture goes away if the company does. Embed.Art names that host on the token's page rather than passing the drawing off as chain data, and the address it uses is the one the project's own API publishes for the token.