Product tour · Agent Catalog

See how Tokynd Troupe works — end to end

One catalog of every agent you run. Troupe registers each agent with its signed manifest, its owner, and its scope — so 'what agents do we have?' always has an answer.

STEP 01

Register

An agent joins the catalog with a signed manifest: what it is, who owns it, what it may touch.

STEP 02

Bind

The entry binds to the agent's Namesake identity and its Referee policy template — no orphan listings, no mystery agents.

STEP 03

Discover

Anyone on the team answers 'what agents do we run?' from one catalog: owner, scope, status, history.

STEP 04

Govern the lifecycle

New versions, scope changes, and retirements flow through the same human gates as everything else on the platform.

Watch it run

Troupe is in build. This is the designed run, stage by stage.

catalog · designed flowtokynd
# signed manifest — as designed agent support-agent · v3 owner AI platform scopes crm.records.read · kb.search policy referee-template: support-tier
Listedcatalog · support-agent

One entry, fully bound

Identity from Namesake, policy from Referee, status live — the catalog entry carries the same record the rest of the platform enforces.

Owner AI platformStatus active
✓

Scope change requested — a widening goes to the named owner and security — the same gate as a new registration

✓

Retirement — the agent is retired in the catalog, its identity revoked through Namesake, the record kept

A worked example — the designed flow

Illustrative catalog entry

InputAn agent + its signed manifest
BindingIdentity from Namesake, policy template from Referee
OutputA catalog entry: owner, scope, status, history
GateLifecycle changes pass the platform's human gates
In buildIn build — design partners get first access.
← All product tours Register interest