Agents

The Agents area shows every instrumented deployment that has sent traffic to Parlot.

Portfolio (/agents)

Each row in the portfolio table represents an agent identity from your SDK configuration (typically the agent_id and optional version you pass to parlotize()). Rows surface recent activity, health, and shortcuts into the workspace.

If the list is empty, complete the SDK Quick Start and run a real or test session so telemetry can register the deployment.

Agent workspace (/agents/:agentId)

Open an agent for a deeper view. Tabs typically include:

• Overview — Volume, outcomes, and high-level trends for this deployment.
• Quality — Goals, sentiment, topics, and evaluation signals for this agent.
• Latency — Turn and pipeline latency for this agent.
• Cost — Spend attributed to this agent.
• Topology — How this deployment hands off among specialized agents (see also the session Topology tab).
• Topics — Topic catalog for this agent (labels, reuse versus newly created topics).
• Versions — Version history when you stamp versions in the parlotize() call.
• Settings — Overrides for recording, log capture, and related agent-scoped policies (same allowlist modes as organization Settings).

How agents appear

Agents appear after instrumented traffic arrives. Keep agent_id stable across releases so history stays on one row; bump version when you want to compare releases.

Related settings

Organization-wide defaults that affect agents live under Settings. Recording, logs, Gen AI content capture, and personally identifiable information (PII) redaction share Agent policy allowlists:

• Recording
• Session logs and capture
• PII redaction
• Conversation boundaries