Dock Certs
for LuumenAI

Check credentials, keys, and webhooks in Dock Certs, then change them on approval

Connect Dock Certs and your agent can look up a verifiable credential, resolve a DID document, list revocation registries, and verify a presentation without leaving the terminal. Changes — new API keys, new webhook endpoints, deletions — are previewed first and wait for your approval by default. Luumen authenticates with an API key.

The Dock Certs 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 Dock Certs run looks like inside Luumen.

Questions

How does LuumenAI connect to Dock Certs?

Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.

Can LuumenAI change things in Dock Certs on its own?

Read actions answer immediately. Anything that writes — create api key, create webhook, delete api key, delete credential, and more — is shown as a plan and requires approval by default, including the 4 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.

Who gets access to the integration?

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.

Is there an audit trail?

Every call to Dock Certs — 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.

Put Dock Certs to work with Luumen

Connect in minutes. Every action scoped, approved, and audited from day one.