Somewhat orthogonal but reminds me of the old map makers who used to insert made up islands / villages on their maps in order to prevent plagiarism. More here: [https://en.wikipedia.org/wiki/Fictitious_entry]
Hah, even more orthogonally but - I run a small statistics site for a specific esports title, and very often large companies (who host tournaments with hundreds of thousands of dollars in production and prize money) just use data from the site in their production without even crediting it. I added a bunch of very innocuous and subtle changes to some data somewhat akin to trap streets - specific values rounding in key ways, slight ordering changes for lists, etc.
You could probably monetize that service with a public API. Then screw over companies that take advantage of your services by providing them data that makes them liable, e.g. if they use it in gambling and they award the wrong prizes.
There is a public API, and yeah many gambling sites use it as a reference when paying out stakes. They sometimes even screenshot from it - and punters tag me because the bookmaker messed up (for example, including qualifiers in a specific tournament market).
A relative has a business publishing information about high school athletics. They created a fictitious school and used it to prove a company had infringed their copyright.
Thankfully the supreme court saved us from an epidemic of misinformation pollution with Feist v. Rural by making it not good for making them any money.
