Pick the right API mode for your use case — Forward Mode for rapid delivery, Build Mode for full runtime control.
Qoder Cloud Agents is a fully managed Agent-as-a-Service platform. It handles Agent construction, deployment, execution, API integration, IM channel delivery, and identity isolation — so your team can ship an AI Agent in hours instead of weeks.
The API has two modes and a shared resource layer that together cover the full Agent lifecycle from development to production.
The fastest way to deploy an Agent in a business scenario. Administrators define Agent behavior through a three-level configuration hierarchy (Enterprise → Template → User). Callers pass a
A low-level, fully managed runtime for developers who need complete control. Define an Agent, start a Session, and dynamically mount sandbox environments, Skills, and files at runtime. No need to build your own agent loop or tool-execution infrastructure.
A shared asset catalog — environments, Skills, credentials, files, memory stores, and model registries — shared by Forward Mode and Build Mode. Define once, reuse everywhere.
Start with Forward Mode to deliver Agent capabilities to end users fast. Choose Build Mode when you need full runtime control and plan to build your own product layer. Both modes share resources from the Resources layer.
What Qoder Cloud Agents does
Qoder Cloud Agents is a fully managed Agent-as-a-Service platform. It handles Agent construction, deployment, execution, API integration, IM channel delivery, and identity isolation — so your team can ship an AI Agent in hours instead of weeks.
The API has two modes and a shared resource layer that together cover the full Agent lifecycle from development to production.
Forward Mode
The fastest way to deploy an Agent in a business scenario. Administrators define Agent behavior through a three-level configuration hierarchy (Enterprise → Template → User). Callers pass a template_id and identity_id — everything else is preconfigured. Built-in IM channel integration, scheduled tasks, and per-user identity isolation come out of the box.
Build Mode
A low-level, fully managed runtime for developers who need complete control. Define an Agent, start a Session, and dynamically mount sandbox environments, Skills, and files at runtime. No need to build your own agent loop or tool-execution infrastructure.
Resources layer
A shared asset catalog — environments, Skills, credentials, files, memory stores, and model registries — shared by Forward Mode and Build Mode. Define once, reuse everywhere.
Forward Mode vs Build Mode
| Forward Mode | Build Mode | |
|---|---|---|
| Positioning | High-level layer atop Build Mode. Adds three-level config, IM channels, scheduling, and identity management for fast, reliable Agent delivery. | Low-level, fully managed Agent runtime. Exposes atomic interfaces for maximum flexibility. |
| Best for | SaaS teams, business integrators, high-volume consumer-facing products | Engineering teams that need full control over Agent behavior and build custom upper-layer systems |
| Configuration | Enterprise / Template / User hierarchy. Callers only pass template_id + identity_id. | Caller specifies environment, Skills, and files at Session creation. |
| Caller complexity | Low — Forward Mode absorbs business complexity. | High — full flexibility; each call decides what to mount. |
| End-user identity | Built-in. One Identity per user; memory and permissions isolated automatically. | Not built in. Caller manages isolation. |
| IM channels | Built-in Feishu, DingTalk, WeChat, WeCom. QR-code binding. | Self-implemented. |
| Scheduling | Built-in Schedules (cron / one-shot). Effective on save. | Self-orchestrated via Deployments. |
Next steps
- Forward Mode — Templates · Identities · Sessions · Schedules · Channels
- Build Mode — Agents · Sessions · Deployments · Dreams
- Resources — Environments · Skills · Vaults · Files · Memory Stores · Models