zlacker

You can serve non-HTML content from Workers. This is explicitly called out in the supplemental terms for the Developer Platform here:

https://www.cloudflare.com/supplemental-terms/

(I'm the lead engineer on Workers. I don't know what happened to OP, though; I'm not personally looped into that conversation.)

>>kenton+(OP)
Another comment says "From what I understood is that it requires a manual over-ride on R2/ Workers because the thing that checks for the 2.8 TOS violation is not able to see the difference between Workers/ R2 and the standard CDN service. If you go to the R2 Discord channel you see this happening every other week"

Is that at all plausible?

>>kenton+(OP)
Maybe I'm missing something, but I don't think that's explicit at all (I've tried to understand this before). The only mentions of HTML are in "(iv) Workers KV, Durable Objects, and R2, storage offerings used to serve HTML and non-HTML content": Workers KV, not Workers.

Meanwhile, section "2.8 Limitation on Serving Non-HTML Content" of the terms says: "The Services are offered primarily as a platform to cache and serve web pages and websites. Unless explicitly included as part of a Paid Service purchased by you, you agree to use the Services solely for the purpose of (i) serving web pages as viewed through a web browser or other functionally equivalent applications, including rendering Hypertext Markup Language (HTML) or other functional equivalents, and (ii) serving web APIs subject to the restrictions set forth in this Section 2.8. Use of the Services for serving video or a disproportionate percentage of pictures, audio files, or other non-HTML content is prohibited, unless purchased separately as part of a Paid Service or expressly allowed under our Supplemental Terms for a specific Service. If we determine you have breached this Section 2.8, we may immediately suspend or restrict your use of the Services, or limit End User access to certain of your resources through the Services."

Serving a "disproportionate percentage of [...] non-HTML content is prohibited". To my understanding, that means that web APIs are allowed, but only if they don't return a disproportionate percentage of non-HTML, since the supplemental terms don't expressly allow it (e.g. no JSON-only APIs).