Sorry for the misquote. I guess that my misquote completely misrepresents the issue?
I never said the data should be not provided in an API.
If you read closely (for more than only "errors"), then you would observe the word "option".
That word is there for a reason.
The role of the FTP site (or whatever protocol you prefer) is to transfer the raw data in bulk to my local media.
Then I move it into my own database of choice and write my own code to access it.
Anyway, fear not. Your preferred www "API" world is not in jeopardy.
Cogent arguments why raw, bulk _public data_ _should never be provided_ in addition to rate-limited, by the slice snippets via "APIs" and third party "app developers" are welcome.
"...is not in the public domain, but can be accessed in small pieces..." (emphasis added)
Besides, this data should absolutely be provided in an API. An exporter tool that queries the API is superior to a static ftp site.