Get Agent
Retrieve the full configuration of an agent — tools, graph, output schema, webhook URL, and all settings
Returns the complete agent object including its tools with full schemas, the tool graph with customized input/output schemas, structured output schema, webhook URL, LLM settings, and all configuration details. This is the single source of truth for an agent’s current state.Documentation Index
Fetch the complete documentation index at: https://docs.xpander.ai/llms.txt
Use this file to discover all available pages before exploring further.
Path Parameters
Response
Identity & Status
emerald-emu). Assigned on creation.instructions. Describes what the agent does.🚀)male-avatar)ACTIVE (deployed) or INACTIVE (not yet deployed)null when created_by is empty or the user cannot be resolved — null-check before reading sub-fields.Instructions
"Short answer, formatted in rich markdown text.").Model Configuration
openai, anthropic, bedrock, gemini, etc.gpt-5.2, claude-sonnet-4-5-20250929)low, medium, or highnull for default provider endpoints.Structured Output
text, json, or markdownoutput_format is json, this is a full JSON Schema that the agent’s output must conform to. Includes $schema, type, required, properties with types, descriptions, validations, and nested objects/arrays.Tools
body_schema and parameters). These are the actual tool-calling interfaces the LLM sees at runtime.Tool Graph
Attached Tools (Toolkit References)
Webhook & Entry Points
agent_id and asynchronous query parameters.Agent Framework Settings
agno)manager, regular, a2a, curl, or orchestration. Agents with type orchestration are Workflows — visual multi-step pipelines.serverless or containerKnowledge Bases
[] if none attached.PATCH endpoint.Other Fields
personal or organizationalExample Request
Example Response
The response is the complete agent configuration. Below is a condensed example showing the key structures — a real response includes full tool schemas and may be 1000+ lines.Common Use Cases
Quick Status Check
List All Tool IDs and Paths
Extract the Output Schema
Get the Webhook URL
Inspect Graph Wiring
See how tools are connected and which have custom schemas:Extract Tool Body Schema for a Specific Tool
Check Attached Toolkit References
attached_tools maps toolkit UUIDs → operation IDs. To manage which tools are attached, use the xpander.ai dashboard or the Python SDK. The REST API PATCH endpoint does not support modifying attached_tools.Authorizations
API Key for authentication
Path Parameters
Response
Successful Response
serverless, container - AIAgentConnectivityDetailsA2A
- AIAgentConnectivityDetailsCurl
- Connectivity Details
personal, organizational Enumeration of possible agent statuses.
Attributes: DRAFT: Agent is in a draft state. ACTIVE: Agent is active and operational. INACTIVE: Agent is inactive and not operational.
DRAFT, ACTIVE, INACTIVE 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. Orchestration: marks the agent as an Orchestration object.
manager, regular, a2a, curl, orchestration openai, nim, amazon_bedrock, azure_ai_foundary, huggingFace, friendlyAI, anthropic, gemini, fireworks, google_ai_studio, helicone, bytedance, tzafon_lightcone, open_router, nebius, cloudflare_ai_gw low, medium, high, xhigh text, markdown, json, voice xpander, custom Configuration for event-based notifications.
Attributes: on_success: Notifications to send when an operation succeeds. Maps notification types to a list of notification configurations. on_error: Notifications to send when an operation fails. Maps notification types to a list of notification configurations.
Configuration object for task-level execution strategies.
This model groups optional strategy configurations that control how a task is executed and managed over time, including retries, iterative execution, stopping conditions, and daily run limits.
Attributes: retry_strategy: Optional retry policy configuration that defines how the task should behave when execution fails (e.g., max attempts, backoff rules).
iterative_strategy:
Optional iterative execution configuration for tasks that may run in
repeated cycles/steps until completion or a stop condition is met.
stop_strategy:
Optional stopping policy configuration that defines when the task
should stop running (e.g., timeout, max iterations, success criteria).
max_runs_per_day:
Optional limit on how many times the task is allowed to run within a
24-hour period. If not set, no explicit daily limit is enforced.
agentic_context_enabled:
if agentic memory is enabled and accesible to the executor.
