Several reads in one round trip

Runs up to 20 GET requests against the read endpoints and answers each with its own status and body, in the order sent. The batch itself is 200 once the envelope is valid, even when every item failed, so read each item's status. An item naming anything that is not a batchable read is refused on its own with allowed_paths attached; the others still run.

Each item is dispatched in-process to the endpoint it names, with your Authorization and Cookie forwarded, so a sub-response is exactly what that endpoint would have returned on its own. Each item counts against its endpoint's own rate limit; the batch saves round trips, not budget.