Dashboard Guide
The Elydora Console is a web-based interface for managing agents, browsing operations, and generating compliance exports.
Accessing the Console
The Elydora Console is available at console.elydora.com. Sign in with the email and password you registered with via POST /api/auth/sign-in/email (Better Auth), or accept an invitation from your organization admin.
Dashboard Overview
The main dashboard displays a summary of your organization's activity: total operations submitted, active agents, recent operations, and the current epoch status. Use the dashboard to quickly assess the health of your Elydora deployment at a glance.
Agents
The Agents page lists every registered agent in your organization. For each agent you can see its ID, label, status (active, frozen, or revoked), public key ID, and the timestamp of its last operation.
- Register — Add a new agent by providing a display name and optional responsible entity. The console generates a unique Agent ID and Ed25519 keypair in your browser (only the public key is sent to Elydora). After registration, the console presents a two-step setup flow:
- Step 1: Credentials — View and copy your private key, Agent ID, Key ID, and Org ID. The private key is shown only once — save it immediately.
- Step 2: Integration Selector — Choose your AI coding tool. For supported tools (Claude Code, Cursor, Gemini CLI, Kiro CLI, Kiro IDE, OpenCode, Copilot CLI, Letta Code), the console shows a one-command install with all credentials pre-filled in Node.js, Python, and Go tabs. For other tools (OpenAI Codex, Kimi, custom enterprise agents, GUI agents), the console shows a step-by-step SDK code tutorial with pre-filled credentials. See the AI Agent Integration guide for details.
- Freeze — Temporarily suspend an agent. Frozen agents cannot submit new operations but their history is preserved. Corresponds to POST /v1/agents/:agent_id/freeze.
- Unfreeze — Reactivate a frozen agent, restoring its ability to submit operations. Corresponds to POST /v1/agents/:agent_id/unfreeze.
- Revoke — Permanently revoke an agent's key. Past operations remain verifiable, but the agent can never submit new operations. Corresponds to POST /v1/agents/:agent_id/revoke.
Operations
The Operations page provides a searchable, paginated view of all submitted Elydora Operation Records (EORs). Each row shows the operation ID, agent, operation type, subject, action, and timestamp. Click any operation to view its full EOR including the payload, chain hash, signature, and the corresponding Elydora Acknowledgement Receipt (EAR).
Audit Trail
The Audit Trail page allows you to query operations with filters. You can filter by agent ID, operation type, time range, or subject. This is the primary interface for compliance investigations — use it to trace exactly what actions an agent performed during a specific window.
Epochs
The Epochs page displays the Merkle tree rollups (Elydora Epoch Roots) that periodically anchor your operation history. Each epoch shows its epoch ID, the number of operations it covers, the Merkle root hash, and its start and end timestamps. Epochs provide bulk-verifiable snapshots of your entire operation history.
Exports
The Exports page lets you create compliance exports of your operation data. Select a time range, agent filter, or operation type filter, then export the results as JSON or PDF. Exports include the full EOR and EAR for each operation, suitable for regulatory submissions and internal audits.
Settings
The Settings page displays your organization information, including your organization ID, registered email, and account creation date. Use this page to manage your account details.
JWKS
The JWKS page shows the Elydora platform's public keys in JSON Web Key Set format. These are the keys Elydora uses to sign Acknowledgement Receipts (EARs). You can use these keys to independently verify that receipts were issued by Elydora. The JWKS endpoint is also available programmatically at GET /.well-known/elydora/jwks.json.
Next Steps
- Follow the Getting Started guide to submit your first operation
- Read the API Reference to understand the endpoints behind each console feature
- Configure RBAC roles to control access within your organization
- Review Security best practices for key management