Agents
Create and configure an agent
Create reusable resources first—prompt templates, skills, connections, and Files folders—then reference their IDs or slugs from the agent.
curl -X POST "$CENTRAL_HUB_URL/api/v1/agents-v2/agents/" \
-H "Authorization: Bearer $TOKEN" \
-H "X-Space-Slug: acme" \
-H "Content-Type: application/json" \
-d '{
"name": "Contract analyst",
"description": "Answers questions about the contracts workspace",
"system_prompt": "You are a careful contract analyst. Cite the source file for every conclusion.",
"model_config_id": 12,
"tool_names": ["files-search", "code-execution"],
"enabled_skill_slugs": ["contract-review"],
"enabled_connection_ids": [42],
"enabled_mcp_connection_ids": [7],
"enabled_file_scope": {"file_ids": [], "folder_ids": ["legal-folder-id"]}
}'tool_names enables runtime abilities. Skills and skill sets add reusable operating instructions. enabled_file_scope limits which Alo Files files or folders the agent can search. Standard and MCP connection IDs are resolved at run time and remain subject to ownership and space permissions.
Update with PATCH /api/v1/agents-v2/agents/{agent_id}/. Use the catalog endpoints to list models, prompts, skills, skill sets, and tools. Agents can be exported/imported as bundles between environments.