{"ops":[{"insert":"So here's the thing, we don't want to have to be held responsible for keeping up with detailed API documentation or fixing issues caused by having an open API. \n\nHowever, our API is open and public (as far as reading is concerned). If you want to reverse engineer how to use it by messing with some filters and watching your chrome network tab, there's nothing preventing you from doing so today. Someone in fact has already done this and wrapped it into an "},{"attributes":{"link":"https://www.npmjs.com/package/archidekt"},"insert":"npm package"},{"insert":". Keep in mind we have no affiliation with them, we don't maintain that or really have any contact with whoever created that. \n\nEDHRec already pulls out data into their site by using these requests and we hope that others will as well to increase the amount of cool stuff available for Magic players.\n\nAll that in mind, if it ever gets to a point where we're getting constantly hammered by requests that aren't ours and it's causing issues -- we'll have no choice but to lock down the API entirely for ourselves and people who we are officially affiliated with.\n\nIf you do pull our data we ask that you link back to Archidekt in some way as well if you're posting that data publicly. Users work hard on brews so giving them credit is a nice thing to do if you're using specific brews. Basically as long as we can continue to operate this way without the internet being an asshat we'd like to do so -- but obviously as we grow this likely could become an issue. If that's the case, we'll come up with a solution.\n\nRight now it's just tough to justify closing that data off from people when they could click through every (public) deck on the site and copy the data somewhere else.\n\nHopefully this helps and spreads a little light onto our thought process over here.\n\nCheers,\nMichael\n"}]}