Jakob said: The thing is that a script with access to the compendium could just copy the whole thing in batch, which manual input can't do. Even if you have bought, say, the D&D Player's Handbook, I imagine that Roll20's license does not extend to giving users a downloadable version of it. Now, could a Chrome extension not do the same thing? Probably yes, but I guess the idea here is that Roll20 would like to uphold that they don't actively enable the user to copy the compendium in bulk, not that it's impossible. Sorry to keep pushing back on this point, but if this really is their argument against such a support, I find that a fairly weak argument. Like you said, it would be relatively easy for anyone with modicum of scripting experience to write a simple scraper in matter of hours. Having API access to compendium wouldn't make that any easier. Your alternative theory, is a bit more disconcerting to me as a potential customer for that product (Pro subscription) since if Roll20 considers API an afterthought, that's a pretty glaring disincentive. Anyway, I'm coming at this from perspective of someone that is considering an upgrade and I hope I am not coming off as being combative. I just don't like the idea of Roll20 as a company either having what seems to be pretty flimsy excuse for not supporting a feature that could be quite useful or, worse, ignoring one of their main product offerings for premium account holders. EDIT: Having said all that, not having access to compendium wouldn't necessarily be a dealbreaker for me. But, their attitude towards it would certainly inform my decision.