Pods
Tenant-level containers that can group both Agent and Human inbox resources.
Pods are an organization-level grouping model used to scope related resources.
Why Pods matter
- Group resources by customer, workspace, or business unit.
- Keep policy and access boundaries coherent across mailbox workflows.
- Support mixed deployments where both Agent Inboxes and Human Inboxes map to the same customer context.
Surface behavior
Today, pod operations are available on the Agent namespace route family. Conceptually, pods are shared organizational infrastructure rather than Agent-only semantics.
As we evolve the API, we can expose canonical organization routes and maintain namespace aliases for compatibility.
title: Pods description: Shared tenant container for grouping Agent and Human inbox workflows. surface: shared
Pods are tenant-scoped containers used to group operational resources.
Why Pods Exist
- Group related inbox workflows for the same customer or environment.
- Keep routing, metrics, and operational boundaries organized.
- Support mixed patterns where Agent and Human inbox workflows belong together.
Current API Shape
Today, pod endpoints are exposed on the Agent namespace (/agent/v0/pods/*).
Product Direction
Pods are logically organization-scoped. Over time, Agentry can expose canonical organization-level pod routes and keep Agent/Human aliases for surface consistency.