How should API chains work with request rate limiting?

There is only one request/response in a chain. All endpoints use the same request/response and that request/response is SHARED oin the backend; this is why it is so fast.

Since the request/response is shared, this really does not effect request per x-time EXCEPT in counting number of endpoints called per x-time.

It WILL count each endpoint called (if you are referencing 'rate limiting') when doing batching and/or chaining.

And the chain is limited in size currently via the variable in beapi_api.yml: apitoolkit>apichain>limit

Currently there is no 'data limit' imposed in the RULES as I am not a fan of sending big amounts of data and I consider 'data limiting' a panacea for bad development (though there is development variable and skeletal development for the functionality).Their is enough built in methodology so it would be easy enough to add.

My apologies for not responding quickly. I need to set the notifications on this forum.

If you are experiencing any problems with this, let me know.