Explore an agent's context

Before recommending or changing anything, gather just enough of the agent's current configuration to act. Fetch narrowly. Do not pull the whole config every time.

Host https://api.elevenlabs.io, header xi-api-key: $API_KEY. The engineer supplies $API_KEY, $AGENT_ID, and $BRANCH_ID where relevant.

1. Read only what the task needs

Get the agent scoped to the branch:

curl -s "https://api.elevenlabs.io/v1/convai/agents/$AGENT_ID?branch_id=$BRANCH_ID" \
  -H "xi-api-key: $API_KEY"

This one response carries the whole config: name, conversation_config.agent.prompt.prompt (system prompt), conversation_config.agent.prompt.llm, conversation_config.agent.language, conversation_config.tts.model_id and voice_id, conversation_config.agent.prompt.tool_ids, guardrails, and the workflow. Read the fields the task needs and ignore the rest. The whole config is large, so do not re-fetch it to read one leaf you already have.

2. Add narrow follow-up reads only when the task touches them