Feature summary

In the existing API that I use for Wikidata I specify a maxlag as described in https://www.mediawiki.org/wiki/Manual:Maxlag_parameter

It would be nice either to have a similar feature in the REST API or some similar feature or guidance on what we should do on Wikidata.

Use case(s) I am considering porting a service to use the new REST API but I'm unsure how to deal with rate limiting. Is max lag planned for the REST API or should throttling be done entirely client side? Or should we rely on the server to throw an exception (I don't see such an error code in the swagger ui)

Benefits (why should this be implemented?): If the REST API is going to replace the older API it should have some solution for throttling. Most automated tools around wikibase let you specify maxlag (e.g. https://github.com/maxlath/wikibase-cli/blob/main/docs/config.md#maxlag)