Issue and verify credentials in Paradym, with every change previewed first
Connect Paradym and the agent can read your credential templates, DIDs, DIDComm connections, and issuance or verification sessions while you work. Ask why a session stalled, or which template a holder was offered. When something needs to change — a new credential offer, a verification request, an archived template — the agent shows the call and waits for your approval. Authentication is by API key.
69 tools: 34 read, 35 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Paradym run looks like inside Luumen.
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — activate certificate, archive anoncreds credential template, archive mdoc credential template, archive presentation template, and more — is shown as a plan and requires approval by default, including the 9 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Paradym — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Connect in minutes. Every action scoped, approved, and audited from day one.