How do I connect Dock certs to Operator?

You authorize Dock certs once from your Operator dashboard. Operator holds the connection and refreshes the access token for you, so your agent keeps working with Dock certs without you signing in again.

Can my agent work with issues and pull requests in Dock certs?

Yes. It can open and comment on issues, review pull requests, manage labels, and read project details when you ask. Teams use it to triage incoming work, draft release notes, and post a summary of what changed without leaving chat.

Do I need to write code or manage Dock certs API keys?

No code and no API keys. You authorize Dock certs through a normal sign in and Operator handles the connection, so there is nothing to wire up or host.

Can my agent use Dock certs together with my other apps?

Yes. The same agent reaches every app you connect, so it can move between Dock certs and tools like GitHub, Supabase, Pagerduty in one job, reading from one and acting in another without you wiring anything between them.

← All integrations

Connect Dock certs to OpenClaw on Operator.io

Dock Certs is a platform for issuing, managing, and verifying verifiable credentials and decentralized identities. It helps organizations make data fraud-proof, instantly verifiable, and tamper-resistant.

Developer Tools & DevOps15 actions

Try for free

Automate Dock certs with AI

Operator puts an OpenClaw agent in front of Dock certs. You describe the job from Telegram or Discord and it handles the rest inside Dock certs, picking the right calls from the 15 Dock certs actions and checking its own work as it goes.

Your agent reaches Dock certs directly or through connectors like Composio MCP and Pipedream MCP, which handle the sign in and token refresh for you, so there is nothing to wire up and no API keys to paste.

What your agent can do with Dock certs

Your agent can call any of these Dock certs actions by name as part of a larger task. Ask for the outcome you want and it picks the right ones.

Create API Key

Tool to create an API key. Use when you need to generate a new API key with optional alias and IP allowlist.

Create Webhook

Tool to create a webhook endpoint. Use when you need Dock.io to push event notifications to your service.

Delete API Key

Tool to delete a specific API key. Use after confirming the API key's ID via list_api_keys.

Delete Credential

Tool to delete a verifiable credential. Use after confirming the credential is no longer needed.

Delete Tag

Tool to delete a specific tag. Use when you have a tag ID and want to permanently remove it.

Delete Webhook

Tool to delete a specific webhook. Use after confirming the webhook's ID via list_webhooks.

Retrieve API Key

Tool to retrieve details of an API key. Tries single-key endpoint first, then falls back to listing and filtering.

Retrieve API Keys

Tool to list all API keys. Use when you need to retrieve all API keys for the authenticated account.

Retrieve Credential

Tool 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.

Retrieve Credentials

Tool to retrieve a list of credential metadata. Use when you need to collect credential details with optional pagination or filtering after authentication.

Retrieve DID Document

Tool to retrieve a DID Document by its DID. Use after you have a valid DID to resolve and inspect its DID Document.

Retrieve Revocation Registries

Tool 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.

Retrieve Webhook

Tool to retrieve a specific webhook's details. Use after confirming you have a valid webhook ID.

Retrieve Webhooks

Tool to list configured webhooks. Use when you need to retrieve all webhook endpoints configured for your account.

Verify Credential or Presentation

Tool to verify a verifiable credential or presentation. Use after receiving a credential or presentation from an issuer.

How to connect Dock certs

You authorize Dock certs once from your dashboard. Operator holds the connection and refreshes the access tokens on its own, so your agent keeps working with Dock certs without you signing in again. The same setup unlocks every other app your agent can reach, so you only do it once.

When you are ready, the get started guide walks through standing up your OpenClaw agent.

Common questions about Dock certs

How do I connect Dock certs to Operator?: You authorize Dock certs once from your Operator dashboard. Operator holds the connection and refreshes the access token for you, so your agent keeps working with Dock certs without you signing in again.
Can my agent work with issues and pull requests in Dock certs?: Yes. It can open and comment on issues, review pull requests, manage labels, and read project details when you ask. Teams use it to triage incoming work, draft release notes, and post a summary of what changed without leaving chat.
Do I need to write code or manage Dock certs API keys?: No code and no API keys. You authorize Dock certs through a normal sign in and Operator handles the connection, so there is nothing to wire up or host.
Can my agent use Dock certs together with my other apps?: Yes. The same agent reaches every app you connect, so it can move between Dock certs and tools like GitHub, Supabase, Pagerduty in one job, reading from one and acting in another without you wiring anything between them.