Create a new agent instance from a template. The template can be from your organization or shared from another organization. All agent configuration, tools, sub-agents, and optionally knowledge bases will be replicated into your organization.
Path Parameters
Unique identifier of the template to import (UUID format)
Request Body
Display name for the new agent instance
Description of the agent instance (optional - can customize the template description)
Emoji icon for the agent (optional - defaults to template icon)
Controls whether to import knowledge bases from the template
true: Imports all knowledge bases with their documents and files (if included in template)
false: Imports only agent configuration without knowledge bases
Response
Returns a complete AIAgent object:
Unique identifier for the created agent (UUID)
Display name of the agent
Emoji icon representing the agent
Current deployment status: ACTIVE or INACTIVE
UUID of the template this agent was imported from
Deployment infrastructure: serverless or container
UUID of your organization
System instructions configuration inherited from template Array of role descriptions
Array of goal descriptions
General instructions text
AI model provider (e.g., openai)
Specific model version (e.g., gpt-4o, gpt-4.1)
Agent framework used (e.g., agno)
Array of imported knowledge bases (if with_knowledge_bases: true)
ISO 8601 timestamp of when the agent was created
Example Requests
Basic Import
curl -X POST -H "x-api-key: <your-api-key>" \
-H "Content-Type: application/json" \
-d '{
"name": "My Support Agent",
"description": "Customer support agent from template",
"icon": "🎧",
"with_knowledge_bases": true
}' \
https://api.xpander.ai/v1/agents/template_import/ < template-i d>
Import Without Knowledge Bases
curl -X POST -H "x-api-key: <your-api-key>" \
-H "Content-Type: application/json" \
-d '{
"name": "Support Agent Framework",
"description": "Will add custom knowledge bases later",
"with_knowledge_bases": false
}' \
https://api.xpander.ai/v1/agents/template_import/ < template-i d>
Example Response
{
"id" : "<agent-id>" ,
"name" : "My Support Agent" ,
"description" : "Customer support agent from template" ,
"icon" : "🎧" ,
"status" : "ACTIVE" ,
"origin_template" : "<template-id>" ,
"organization_id" : "<org-id>" ,
"deployment_type" : "serverless" ,
"created_at" : "2026-02-07T10:30:00.000000Z" ,
"instructions" : {
"role" : [ "Customer support specialist" ],
"goal" : [ "Resolve customer issues efficiently" ],
"general" : "Be helpful and professional"
},
"model_provider" : "openai" ,
"model_name" : "gpt-4.1" ,
"framework" : "agno" ,
"knowledge_bases" : [
{
"id" : "<kb-id>" ,
"name" : "Product Documentation" ,
"description" : "Product guides and FAQs"
}
],
"tools" : [],
"graph" : []
}
Import Behavior
When importing a template:
New Agent Created : A completely independent agent instance is created in your organization
Configuration Copied : All agent settings, instructions, and behavior are replicated
Sub-Agents Recreated : Complete agent hierarchy is maintained with new instances
Knowledge Bases : Documents are copied to your organization (if included and with_knowledge_bases: true)
Tools & Connectors : Tool configurations are preserved - you’ll need to provide credentials
Independence : Changes to the imported agent won’t affect the source agent or template
Notes
Cross-Organization Support : Templates can be imported from any organization - share the template ID
Customization : You can modify the agent name, description, and icon during import
Tool Setup : After import, configure credentials for any tools that require authentication
Knowledge Bases : If the template was exported without knowledge bases, with_knowledge_bases: true has no effect
Origin Tracking : The origin_template field tracks which template was used for import
Next Steps
After importing an agent:
Update agent configuration using Update Agent if needed
Configure tool credentials if the agent uses external tools
Deploy the agent using Deploy Agent
Test the agent with sample tasks
See Also
API Key for authentication
Available options:
serverless,
container
Display name of the agent
Agent framework used (e.g., agno)
Description of the agent's purpose and capabilities
Array of tools available to the agent
Emoji icon representing the agent
instructions
AIAgentInstructions · object
graph
AIAgentGraphItem · object[] | null
Current deployment status: ACTIVE or INACTIVE
Available options:
DRAFT,
ACTIVE,
INACTIVE
knowledge_bases
AgentKnowledgeBase · object[] | null
Array of knowledge bases attached to the agent
UUID of the organization that owns this agent
Enumeration of the agent types.
Attributes:
Manager: marks the agent as a Managing agent.
Regular: marks the agent as a regular agent.
A2A: marks the agent as an external agent used via A2A protocol.
Curl: marks the agent as an external agent used via a CURL.
Available options:
manager,
regular,
a2a,
curl
AI model provider (e.g., openai, anthropic)
Available options:
openai,
nim,
amazon_bedrock,
huggingFace,
friendlyAI,
anthropic,
gemini,
fireworks,
google_ai_studio,
helicone,
open_router,
nebius
Specific model version (e.g., gpt-4o, gpt-4.1, claude-sonnet-4-5-20250929)
Output format: markdown or json
Available options:
text,
markdown,
json
JSON schema for structured output when output_format is json
Natural-language description of the desired output (e.g., "A bulleted list of key findings")
Auto-generated webhook URL for agent invocations
Auto-generated unique identifier for the agent (e.g. 'emerald-emu')
Custom LLM API base URL for self-hosted or proxied model endpoints
llm_settings
AIAgentGraphItemLLMSettings · object[]
LLM configuration per graph node (provider, model, temperature)
Agno framework settings (memory, session storage, moderation, tool limits)
Whether the agent has unpublished configuration changes