.movie, .book, .museum, .news, etc.
This would have avoided this problem where you have “book-name-book.com” and “newblockbuster-movie.com” and so on.
It would be a cool alternative to guarantee that example.tld owned example.tld.api though, as you could assume that any .api domain would be an API.
lots of times you don't care about anything on a domain but the api
https://www.californiarailroad.museum/
(no affiliation with them, but was pleasantly surprised to see it in the wild)
I’m not super excited about letting anyone who can afford to run a TLD make one either, but at least so far there appears to be relatively little mainstream appetite for using them.
https://en.m.wikipedia.org/wiki/Uniform_Domain-Name_Dispute-...
The world would be better off without UDRP.