Dock Certs is a platform that enables organizations and developers to issue, manage, and verify verifiable credentials and decentralized identities, making data fraud-proof and instantly verifiable.
Dock Certs is a platform that enables organizations and developers to issue, manage, and verify verifiable credentials and decentralized identities, making data fraud-proof and instantly verifiable. On Nagent, Dock Certs is exposed as a fully-configurable security & identity tools integration that any agent can call — 15 actions, and API key authentication. No code is required to wire Dock Certs into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Dock Certs to automate the kinds of tasks security & identity tools teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Dock Certs into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Dock Certs, with input parameters and output schema. Drop these into any step of an agent built in Helix.
DOCK_CERTS_CREATE_API_KEYTool to create an API key. Use when you need to generate a new API key with optional alias and IP allowlist.
Input parameters
List of whitelisted IP addresses allowed to use the key.
Human-readable name for the API key.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCK_CERTS_CREATE_WEBHOOKTool to create a webhook endpoint. Use when you need Dock.io to push event notifications to your service.
Input parameters
The HTTPS endpoint to which Dock.io will POST event notifications.
List of event types to subscribe to.
Webhook status flag (0 = disabled, 1 = enabled).
Human-readable description for this webhook.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCK_CERTS_DELETE_API_KEYTool to delete a specific API key. Use after confirming the API key's ID via list_api_keys.
Input parameters
Unique identifier of the API key to delete
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCK_CERTS_DELETE_CREDENTIALTool to delete a verifiable credential. Use after confirming the credential is no longer needed.
Input parameters
Identifier of the credential to delete. It can be a full URI; the action will URL-encode it for safe path usage.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCK_CERTS_DELETE_TAGTool to delete a specific tag. Use when you have a tag ID and want to permanently remove it.
Input parameters
Unique identifier of the tag to delete.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCK_CERTS_DELETE_WEBHOOKTool to delete a specific webhook. Use after confirming the webhook's ID via list_webhooks.
Input parameters
Unique identifier of the webhook to delete
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCK_CERTS_RETRIEVE_API_KEYTool to retrieve details of an API key. Tries single-key endpoint first, then falls back to listing and filtering.
Input parameters
Public key identifier of the API key (value of 'key' from /keys).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCK_CERTS_RETRIEVE_API_KEYSTool to list all API keys. Use when you need to retrieve all API keys for the authenticated account.
Input parameters
Maximum number of items to return (1-64).
Number of items to skip for pagination.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCK_CERTS_RETRIEVE_CREDENTIALTool to retrieve a verifiable credential by its unique ID. If a password was used to persist it, include the same password to decrypt and return the full credential. Otherwise, only metadata is returned.
Input parameters
Credential ID as a full URI.
Password supplied at issuance to decrypt stored credential contents. Optional; without it, only metadata is returned.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCK_CERTS_RETRIEVE_CREDENTIALSTool to retrieve a list of credential metadata. Use when you need to collect credential details with optional pagination or filtering after authentication.
Input parameters
How many items to return (min 1, max 100; default 64).
Optional filter string to match Credential ID, Subject Ref, Issuer, Type, Created Date, or Issue Date.
How many items to skip for pagination (default 0).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCK_CERTS_RETRIEVE_DIDTool to retrieve a DID Document by its DID. Use after you have a valid DID to resolve and inspect its DID Document.
Input parameters
Fully qualified decentralized identifier (DID) to resolve (e.g., did:dock:5GJcPXbt8RBhxu7w4GmgYb).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCK_CERTS_RETRIEVE_REGISTRIESTool to retrieve a list of revocation registries. Use when you need to list all registries created by the authenticated account with optional pagination and filtering.
Input parameters
Filter registries where this DID exists in the registry policy.
Filter registries by type.
Maximum number of items to return, between 1 and 64. Defaults to 64.
Number of items to skip for pagination, defaults to 0.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCK_CERTS_RETRIEVE_WEBHOOKTool to retrieve a specific webhook's details. Use after confirming you have a valid webhook ID.
Input parameters
Unique identifier of the webhook (numeric string).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCK_CERTS_RETRIEVE_WEBHOOKSTool to list configured webhooks. Use when you need to retrieve all webhook endpoints configured for your account.
Input parameters
Maximum number of webhooks to return in one call (max 64).
Number of webhooks to skip for pagination.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCK_CERTS_VERIFYTool to verify a verifiable credential or presentation. Use after receiving a credential or presentation from an issuer.
Input parameters
Either a W3C Verifiable Credential or Verifiable Presentation (JSON-LD dict) to verify, or a JWT string representation.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 63 agents privately built on Nagent that already use Dock Certs.
Build on Nagent
Connect Dock Certs to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Dock Certs, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Dock Certs is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Dock Certs is connected, you configure its 15 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Dock Certs steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Dock Certs event fires, the agent kicks off automatically.
Every Dock Certs action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Dock Certs ships with 15 pre-built security & identity tools actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Dock Certs together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Dock Certs-based workflows tailored to your business.