Read one agent

The detail of a single agent. A deleted agent returns 404 agent_not_found. At creation, useForOutboundTasks selects the initial platform: true chooses volai's engine, false ElevenLabs, and omission uses the deployment default. Since POST returns only an id, verify the result in this follow-up GET and its provider field. Enabling transferTo on an ElevenLabs agent triggers an engine switch attempt, but it may be paused, unavailable or fail; handoff does not work while provider remains elevenlabs. A successful switch may change the voice. Changing language with PATCH from a language in which new agents start on ElevenLabs (today en, de, pl) to one in which they start on the engine (cs, sk) triggers the same attempt: on success the agent gets the new language's default engine voice (Milena, Katarina), on failure it stays on ElevenLabs. A change between cs and sk moves nothing. Other provider moves are handled by support. ElevenLabs accepts only anet from the catalog or a raw ElevenLabs voice id; other catalog voices require the engine. The response also always carries a laughterEffective field ({active, reason, sensitiveCategory} | null) - the live laughter-policy outcome for the agent's PUBLISHED configuration, computed fresh outside of any call. For an ElevenLabs agent it's always {active: false, reason: "not_engine", sensitiveCategory: null} without calling the engine; for an engine agent reason is one of several values (ok, agent_off, sensitive_prompt, voice_not_listed and more) and the engine may add new ones over time - treat an unknown value as off, not as an error. When the engine doesn't answer within 3 seconds, is down, or doesn't know the agent (a silent 404 on an older build), laughterEffective is null outright - never a guess.