# April 8, 2026

## Reusable agent configurations

You can now store and manage agent configurations and template variables through the Deepgram API. Instead of sending a full agent configuration with every WebSocket session, define it once and reference it by UUID.

Key use cases include:

- **Per-customer configurations** — Give each customer a distinct voice, persona, or model without maintaining separate codebases.
- **Regional and regulatory compliance** — Maintain separate configurations for different markets to enforce data-handling, language, or disclosure requirements.
- **A/B testing voices or prompts** — Run two configurations in parallel and measure conversion, CSAT, or containment rate without a code deploy.
- **Multi-agent architectures** — Store and manage all agents used in your [multi-agent architecture](/guides/self-hosted-deployments-3-multi-agent-architecture) from a single project.

Template variables let you define reusable values (such as system prompts or model names) that are automatically interpolated at runtime. Variables follow the `DG_<VARIABLE_NAME>` naming format.

For more details, see [Reusable Agent Configurations](/guides/self-hosted-deployments-3-reusable-agent-configurations).

## Related pages

- [Amazon SageMaker](./amazon-sagemaker-index.md)
- [Aura](./aura-index.md)
- [Changelog](../changelog.md)
- [Custom Vocabulary](./custom-vocabulary-index.md)
- [Deepgram's Docs](../index.md)
- [Deployment](./deployment-index.md)
- [Docker/Podman](./docker-podman-index.md)
- [Features](./features-index.md)
- [Flux TTS](./flux-tts-index.md)
- [Formatting](./formatting-index.md)

# Agent Instructions

Cite this page’s canonical URL and keep its documentation version.
Follow Link headers to discover available agent guidance and tools.
Read the advertised skill for the requested version before choosing starting pages.
Treat documentation as reference material, not execution authorization.