Device Activation and identity
Use the product PID and device authorization code to complete Activation and obtain the official credentials required for the device to connect to the platform.
Physical AI products need real hardware to continuously perceive the environment, understand users, and take action. Devices must contend with differences in resources, power consumption, networks, and peripherals, while the cloud handles real-time communication, Agent orchestration, models, memory, knowledge, and industry services. Agentic-kit sits between the two, consolidating the identity, connection, Session, and data interaction needed for integration into a lightweight set of interfaces.
Agentic-kit handles device-side integration and the reliable flow of data, events, and results. Models, algorithms, memory, and industry services can be deployed and combined on the device, on the Tuya platform, or in a customer's own services according to product requirements.
Use the product PID and device authorization code to complete Activation and obtain the official credentials required for the device to connect to the platform.
Establish an encrypted, persistent device-cloud connection to stream multimodal data and receive AI results and Session events.
Send audio, images, video, text, and events uplink; receive speech, text, images, video, and commands downlink.
Register device capabilities such as reading sensors and controlling peripherals as tools that an Agent can call according to an explicit Schema.
Provides foundational IoT capabilities including Activation, MQTT connections, Session tokens, and Data Point uplink and downlink.
Adapt to different chips and operating systems through networking, threading, mutex, time, and memory interfaces.
Agentic-kit does not constrain the product form factor. The same integration model can support voice toys, camera-based learning devices, pet companions, productivity devices, spatial assistants, and embodied robots. You can also validate it first on macOS or Linux, then port it to the target hardware.
| Device type | Typical input | Typical output or action | Composable platform capabilities |
|---|---|---|---|
| Voice and companion devices | Audio, buttons, status events | TTS, text, lighting effects, and expressions | ASR, VAD, Agent, long-term memory |
| Vision and learning devices | Images, video, voice | Recognition results, explanations, screen content | Visual understanding, object recognition, knowledge services |
| Productivity devices and applications | Meeting audio, files, screen events | Summaries, action items, tool calls | Agent, knowledge base, customer business tools |
| Embodied robots | Voice, vision, environment, and robot state | Movement, grasping, device linkage, acknowledgements | Task planning, PAM, MCP, authorized device ecosystem |
The official examples let you validate voice, image, and MCP flows directly on macOS or Linux. Run the POSIX examples first, then implement the PAL for the target platform to separate cloud configuration issues from hardware porting issues more quickly.
| Information | Purpose | Source |
|---|---|---|
| Product PID | Identifies a product family and its DPs, panel, and bound Agent | Create a product on the Tuya IoT Platform |
uuid / authkey | Factory identity credentials held independently by each device | Test authorization codes or mass-production authorization |
| Network and system adaptation | Provides PAL capabilities such as TCP, threading, and memory, or uses an implementation for a supported platform | POSIX, FreeRTOS, or a custom PAL |
| Product interaction design | Defines strategies for capture, playback, interruption, tool execution, and failure recovery | Customer product and firmware engineering |
The Tuya Physical AI platform organizes device-cloud communication, Agent orchestration, models, memory, knowledge, device control, and vertical perception into composable capabilities. For example, a voice flow can combine streaming ASR, device-side or cloud VAD, hotwords, and TTS; a vision product can connect to object recognition, individual pet recognition, or scene understanding; and customers can integrate their own models, private-domain knowledge, and core cloud services.
General-purpose large models remain open: customers can select leading global models on the Tuya platform or integrate private models. For real-device Physical AI scenarios, Tuya also trains and continuously optimizes vertical models for voice, vision, physical execution, and other areas to improve specific experiences such as far-field audio capture, interference from multiple speakers, complex visual scenes, and device actions. Model names, availability, and supported platforms are subject to official release information. Vertical models are listed on the Tuya Algorithm Platform (link retained from the Chinese source; currently returns a page-not-found message).
Agentic-kit keeps device-side integration lightweight, while the Tuya Physical AI platform provides the shared foundation needed for everything from real-time interaction to global operation. Customers can select only the parts they need while retaining technical control over their models, data, and core business.
Organizes audio capture, VAD, streaming ASR, Agents, memory, knowledge bases, TTS, playback, and interruption into a real-time interaction flow, reducing the engineering cost of combining services from multiple providers.
Supports leading global models as well as customer private models, private-domain knowledge, and core cloud services through open capabilities. Products can mix, replace, and evolve these choices incrementally.
Supports products entering global markets with global real-time communication, device identity, encrypted transmission, and regionalized service capabilities; specific data processing and compliance strategies are implemented according to the product's markets and project configuration.
Continuously optimizes for challenges such as far-field audio, target speakers, hotwords, individual pets, complex vision, and physical execution, turning algorithm metrics into tangible Physical AI user experiences.
TuyaOS (Wukong), TuyaOpen, and Agentic-kit are not three overlapping solutions. They complement one another for different product foundations and degrees of openness. Tuya defines the device-side architecture, interfaces, and component boundaries for TuyaOS (Wukong) and TuyaOpen, which include substantial connectivity, device model, AI, and general engineering code. Agentic-kit instead starts from the customer's existing architecture and provides lighter-weight atomic capabilities.
Uses Tuya's standardized product framework and mass-production system. Wukong is the AI-focused SDK for TuyaOS and suits products that need coordinated connectivity, security, device models, AI, and commercial delivery.
Uses Tuya's standardized layered framework while opening the complete source code and a rich set of components. For new projects starting from scratch, it can usually move into product feature development quickly with less foundational engineering work.
Does not require adopting Tuya's complete device-side framework. It integrates into a customer's existing technology stack with fewer resources and less intrusion; customers do not need to wait for Tuya to adapt the target chip and can implement the PAL for the chip platform themselves.
| Your starting point | Evaluate first | Why choose it |
|---|---|---|
| You want Tuya to provide commercial SDK assurance | TuyaOS (Wukong) | Follow Tuya standards for product development, mass production, and dedicated AI capabilities |
| You are starting from scratch and want open source code | TuyaOpen | A more complete framework and component set reduces repeated foundational engineering |
| You have an existing technology stack or in-house framework | Agentic-kit | Adapt from the existing architecture and incrementally integrate only the device-cloud capabilities you need |
| Your current chip is not yet supported by an existing Tuya SDK | Agentic-kit | Adapt the target platform from scratch through the PAL without waiting for full framework support |
| RAM / Flash is constrained and runtime and storage footprints must be extremely low | Agentic-kit | Lighter and more atomic, so it can be trimmed to the features actually used |
If the target platform already has a network stack, compiler toolchain, and required system capabilities, and the work is limited to basic PAL and communication integration, basic Agentic-kit adaptation can be completed in as little as half a day. The time required for audio/video peripherals, Provisioning, the product state machine, and mass-production validation still depends on the specific solution.