Decision guide
Agent Studio
Agent Studio is the fastest way to ship agents. Use it when:- Your team includes non-engineers who need to configure agents.
- You want to iterate on prompts, models, and tools without redeployment.
- You need voice agents, scheduling, or webhook triggers.
- You want built-in evaluation, monitoring, and version control.
Architect
Use Architect when you need a full-stack application, not just an API endpoint. Architect generates the frontend, wires in Studio agents, and self-corrects via a QA agent. Best for: proof-of-concept apps, customer-facing tools, internal dashboards.ADK (Agent Development Kit)
Use the ADK when:- You are integrating Lyzr into an existing Python or TypeScript application.
- You need fine-grained control over agent behavior and retry logic.
- You are building CI/CD pipelines that create or update agents programmatically.
REST API
Use the REST API when:- You are calling from a non-Python language (Node, Go, Ruby, and others).
- You are integrating with an existing API gateway or service mesh.
- You want direct endpoint control without any SDK abstraction.
Lyzr Blocks
Lyzr Blocks are modular components you can use without adopting the full Studio:- Knowledge Base: RAG-as-a-service endpoint; use from LangChain, Semantic Kernel, or any agent framework.
- Cognis: Memory-as-a-service with MCP support; plug into Cursor, Claude, or custom agents.
- Responsible AI: Guardrails-as-a-service; add toxicity, PII, and injection checks to any pipeline.