[Question] Is SlimeRouter + RadixTree intended to be strict TITO gateway?

Your Question

I’m trying to understand current SlimeRouter behavior in RadixTreeMiddleware + proxy path.
From the report, my understanding is:

In middleware, /generate payload is rewritten:

request_json = await request.json()
request_json["input_tokens"] = input_tokens
request_json["stream"] = False
request._json = request_json

But in SlimeRouter.proxy, forwarding uses raw body bytes:

body = await request.body()

My question:
Is this intended (middleware rewrite is only for local cache logic, not for downstream forwarding)?
Or should worker actually receive rewritten /generate JSON (strict gateway/token-in behavior)?
If intended, should docs explicitly state this to avoid confusion around RadixTree “transparent token management”?
I may be misunderstanding the design, so would appreciate clarification from maintainers.

What I've Tried

• I have search issues about this

Environment (if relevant)

Additional Context

No response

Pre-submission Checklist

• I have read the CONTRIBUTING.md and understand the collaboration scope.
• I have read the documentation and FAQ and my question is not answered there.
• I have searched for existing issues and my question has not been asked before.

Start by reading the RadixTreeMiddleware handling of /generate and the SlimeRouter.proxy entry point, comparing the rewritten request JSON with the raw body forwarded downstream. Check the linked documentation and FAQ context. Done means the intended gateway contract is established and, if needed, documented clearly.