Truvera
for LuumenAI
Check credentials, keys, and webhooks in Truvera, then change them with approval
Connect Truvera and your team can ask about credential status, DID documents, revocation registries, API keys, and webhook endpoints without opening the dashboard. Verification runs on request and answers right away. Changes like creating an API key or removing a stale webhook are previewed first and go out as approved, audited steps. Luumen authenticates with an API key.
The Truvera toolbox
15 tools: 9 read, 6 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadRetrieve API KeyRetrieve details of an API key.
- ReadRetrieve API KeysList all API keys.
- ReadRetrieve CredentialRetrieve a verifiable credential by its unique ID.
- ReadRetrieve CredentialsRetrieve a list of credential metadata.
- ReadRetrieve DID DocumentRetrieve a DID Document by its DID.
- ReadRetrieve Revocation RegistriesRetrieve a list of revocation registries.
- ReadRetrieve WebhookRetrieve a specific webhook's details.
- ReadRetrieve WebhooksList configured webhooks.
- ReadVerify Credential or PresentationVerify a verifiable credential or presentation.
- WriteCreate API KeyCreate an API key. Approval by default
- WriteCreate WebhookCreate a webhook endpoint. Approval by default
- WriteDelete API KeyDelete a specific API key. Approval by default
- WriteDelete CredentialDelete a verifiable credential. Approval by default
- WriteDelete TagDelete a specific tag. Approval by default
- WriteDelete WebhookDelete a specific webhook. Approval by default
One prompt, start to finish
What a governed Truvera run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
This connection exposes write actions such as create api key, create webhook, delete api key, delete credential, and more. For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user. Review the configured approval policy before enabling write access.
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 Truvera — 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.
Often connected alongside
All integrations
OktaAccess and posture from Okta, with approval on every change.
Microsoft Entra IDAccess and posture from Microsoft Entra ID, with approval on every change.
Auth0Access and posture from Auth0, with approval on every change.Ping IdentityAccess and posture from Ping Identity, with approval on every change.Put Truvera to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.