What problem does it solve? Integrating ByteDance's ByteTIM traffic identity ticket system requires choosing the correct service role, framework middleware, and initialization order, and mistakes cause missing UserID/DeviceID propagation or failed ticket verification across the RPC chain. ## Core Features & Use Cases - Role-Based SDK Integration: Guides registration and setup for ticket generator versus ticket verifier roles, including version compatibility and user/device type configuration on the ByteTIM management platform. - Framework Middleware Coverage: Provides working code for Ginex, Hertz v0/v1, Kite, KiteX, GDP, and Python Euler frameworks, including session middleware ordering for C-end scenarios. - Custom Parameters & Verification: Shows how to inject custom ticket fields, enable Auth Level and Session App ID, and validate integration via the iesarch.bytetim.client.generate_ticket metrics. - Use Case: A backend engineer building a KiteX RPC service that must propagate user identity downstream can follow the guide to register the PSM, add timkitex middleware, and confirm ticket generation through monitoring metrics. ## Quick Start Ask the agent to show how to integrate the ByteTIM SDK middleware into a KiteX server and verify the integration succeeded.