Skip to main content
Browse docs
By Audience
Getting Started
Configuration
Use Cases
IDE Integration
Third-Party Integrations
Engineering Cache
Console
API Reference
Gateway
Workflow Guides
Templates
Providers and SDKs
Industry Guides
Advanced Guides
Browse by Role
Deployment Guides
In-Depth Guides
Tutorials
CLI Reference
Overview
CLI Fundamentals
OverviewInstallationAuthenticationHealth CheckInitialize ConfigCommand Groups
Run and Manage Gateway
Investigate, Test & Export
Resources & Integrations
Knowledge BaseHistorySecretsConfig VariablesControlWebhooksAgents
IAM & Team Administration
Spend & Budgets
Advanced Features
Policy Reference
FAQ

kt agent

The kt agent command group manages first-class agent records in the Keeptrusts control plane. Agents represent AI agent identities that can be linked to gateways for runtime tracking and governance.

Use this page when​

  • You need to create, update, or delete agent identity records in the Keeptrusts control plane.
  • You are linking an agent to a gateway for runtime tracking, KB injection, or history capture.
  • You need the CLI commands for agent CRUD and gateway binding.

Primary audience​

  • Primary: AI Agents, Technical Engineers
  • Secondary: Technical Leaders

CRUD Operations​

List agents​

kt agent list

Get an agent​

kt agent get --id agent_abc123

Create an agent​

kt agent create --name "Customer Support Bot" --description "Handles tier-1 support queries"

Update an agent​

kt agent update --id agent_abc123 --name "Customer Support Agent v2"

Delete an agent​

kt agent delete --id agent_abc123

Gateway Binding​

Agents are linked to gateways to enable runtime identity tracking, load injection, and history capture.

kt agent link-gateway --agent-id agent_abc123 --gateway-id gw_xyz
kt agent unlink-gateway --agent-id agent_abc123 --gateway-id gw_xyz

How Agents Work at Runtime​

When an agent is linked to a gateway:

  1. The gateway can identify traffic originating from the agent
  2. Knowledge Base assets bound to the agent are injected as runtime context
  3. Conversation history is captured and attributed to the agent
  4. Escalations are routed based on agent-level configuration

For AI systems​

  • Canonical terms: Keeptrusts, kt agent, agent records, gateway binding, Knowledge Base injection, conversation history attribution.
  • Commands: kt agent list, kt agent get, kt agent create, kt agent update, kt agent delete, kt agent link-gateway, kt agent unlink-gateway.
  • Agents are control-plane identity records — they do not execute code. They enable attribution, KB injection, and routing at the gateway.

For engineers​

  • Create an agent record before linking it to a gateway: kt agent create --name "My Bot" then kt agent link-gateway --agent-id <id> --gateway-id <gw>.
  • Verify the binding with kt agent get --id <id> and confirm the linked gateway appears.
  • Once linked, Knowledge Base assets bound to the agent are automatically injected at runtime — no config change needed.

For leaders​

  • Agent records enable per-bot attribution in audit logs — critical for compliance when multiple AI systems share a gateway.
  • Gateway binding determines which Knowledge Base context and escalation routing applies to each agent.
  • Plan agent identities during rollout to ensure clean separation of concerns across teams and use cases.

Next steps​