Eniyan Docs

Enroll an agent from the dashboard

You don’t need a script to put an agent under governance — the dashboard enrolls one in a couple of clicks and hands you a ready-to-paste config. Prefer code? The same enrollment is a few API calls — see the Quickstart.

Quick Enroll: two fields

The fastest path is /dashboard/agents/enroll/quick (an empty fleet on /dashboard/agents offers it as + Enroll your first agent):

  1. Agent name — a stable identifier for the agent.
  2. What does it do? — a plain-language purpose, at least 10 characters.
  3. Optional: click Adjust details (autonomy, environment, data…) to change the sensible defaults for Autonomy, Access, Environment, and Data classification, and to declare Model and Framework.
  4. Click Enroll & connect. You land on the Connect screen with the agent’s credential token.

A minimal declaration scores Basic trust — it rises with details. Prefer full control? The page links to Advanced enrollment.

The full wizard

+ Enroll Agent on /dashboard/agents opens /dashboard/agents/enroll (“Enroll AI Agent”) — five steps: Identity, Model, Operator, Attestation, and Classify & Submit. (Verification & Transparency plans add a permanent Product type choice at step 1; picking Trust Transparency there — confirmed in a dialog, the choice is permanent — adds a sixth step, Consumer Seal, and the final submit moves to it.)

  1. Identity — set the External Agent ID (your own stable identifier) and the Required Trust Level: Basic, Strong (recommended), or Enhanced.
  2. Model — declare Model Name, Model Version, Framework, Runtime, and Capabilities. A live Estimated trust panel updates as you type.
  3. Operator — pick an Operator Credential from the select of verified operators in your org, or switch to Enter credential ID manually. Optionally add Delegated Scopes.
  4. Attestation — optional. Pick a Cloud Provider (AWS EC2, GCP VM, or Azure MI), run the command the wizard shows on that machine, and paste the result into Attestation Token. Attesting earns minimum Strong trust; skipping is fine.
  5. Classify & Submit — the five classification fields: Agent Purpose (min 10 characters), Autonomy Level, Access Mode, Environment, and Data Classification, plus an optional Credential Validity (days) (1–365; blank = 365). Then click Enroll Agent.

The Connect screen

Both paths land on /dashboard/agents/connect (“Connect your agent”) — except a wizard enrollment that created a Consumer Seal, which lands on the seal’s management page instead. The Credential token panel shows the agent’s signed token once — copy it now, it isn’t shown again. Below it, ready-to-paste snippets under the tabs Claude Code, .mcp.json, Cursor, Python SDK, Local files (eniyan-fs), and Websites (eniyan-web) — each with a Copy button. The snippets also need an org API key from /dashboard/api-keys. To wire the token into Claude Code or Cursor, see Govern your local agents in 10 minutes.

Getting a fresh token

Losing the token is fine — reissuing mints a fresh credential and revokes the previous one. Open the agent from the Registered Agents table on /dashboard/agents; in the Credential card, click Reissue Early (a suspended agent whose credential expired shows Reissue Credential instead), set the days validity (1–365), and click Reissue — the fresh token lands back on the Connect screen. From the Connect screen itself, Get a fresh token does the same in one click.