ceven

Dock Certs

Issues and verifies fraud proof credentials for your users and monitors revocation registries to keep identity data current in real time.

Try Dock Certs in Ceven

Ask Ceven anything
Standard

Why use Ceven?

  1. AI native Dock Certs integration

    • Describe the outcome and Ceven picks the right Dock Certs calls, fills the parameters, and checks the result.
    • Structured, agent friendly tool schemas so each call runs reliably instead of by guesswork.
    • Rich coverage for reading, writing, and querying your Dock Certs data, across all 15 of its actions.

  2. Managed auth

    • Built in OAuth with automatic token refresh and rotation.
    • One place to manage, scope, and revoke Dock Certs access.
    • Per user and per environment credentials instead of shared keys.

  3. Agent optimized design

    • Actions are tuned from real success and error rates so reliability climbs over time.
    • Full execution logs so you always know what ran in Dock Certs, when, and on whose behalf.
    • The agent pauses and asks when Dock Certs is unclear instead of plowing ahead.

  4. Enterprise grade security

    • Fine grained access so you control which agents and people can reach Dock Certs.
    • Least privilege by default, read scopes first and only the writes a workflow needs.
    • A full audit trail of every Dock Certs action to support review and sign off.

Supported tools

Every action Ceven's agents can run on Dock Certs, and when to use it.

Create API Key
Use this to generate a new API key with an optional alias and IP allowlist for secure access.
Create Webhook
Set up a webhook endpoint so Dock Certs can push event notifications to your external service.
Delete API Key
Permanently remove a specific API key after confirming the ID via the list keys tool.
Delete Credential
Remove a verifiable credential from the system when it is no longer needed or valid.
Delete Tag
Use this when you have a specific tag ID and want to permanently remove it from the platform.
Delete Webhook
Remove a specific webhook endpoint using its unique ID to stop receiving event notifications.
Retrieve API Key
Pull details of a specific API key by trying the single key endpoint first then falling back to lists.
Retrieve API Keys
List all API keys associated with the authenticated account to audit active access tokens.
Retrieve Credential
Pull a verifiable credential by ID. Include the persistence password to decrypt the full credential or get metadata.
Retrieve Credentials
Pull a list of credential metadata with optional pagination and filtering for account auditing.
Retrieve DID Document
Resolve a specific DID to pull and inspect its associated DID Document for identity verification.
Retrieve Revocation Registries
List all revocation registries created by the account to check the status of issued credentials.
Retrieve Webhook
Pull the configuration details of a specific webhook using its unique identifier.
Retrieve Webhooks
List all configured webhook endpoints to verify where identity events are being sent.
Verify Credential
Verify a verifiable credential or presentation received from an issuer to ensure authenticity.
Verify Credential or Presentation
Tool to verify a verifiable credential or presentation. Use after receiving a credential or presentation from an issuer.

16 actions · scroll to see them all

Frequently asked questions

Ceven can retrieve both metadata and full encrypted credentials. When a credential was persisted using a password, the full content remains encrypted on the Dock servers. To pull the actual data, the workflow must provide the matching password during the retrieval call. If no password is provided, the agent only receives the metadata such as the issuance date and credential type. You should store these passwords in a secure vault and have the agent pull them at runtime to ensure that sensitive identity data is never stored in plain text within your workflow logs or prompt history.
Yes. Ceven can interact with the revocation registries to mark specific credentials as invalid. This is commonly used when a professional certification expires or an employee leaves an organization. The agent monitors the expiration date in your database and calls the appropriate registry tool to update the status. Once revoked, any subsequent attempt to verify that credential using the verify tool will return a revoked status, ensuring that your identity ecosystem remains accurate and secure without requiring a human to manually update each record in the Dock dashboard.
Ceven can create, list, and delete API keys, but it cannot rotate them automatically in a single step. You must first create a new key and then delete the old one. A critical quirk of the Dock Certs API is that some tier gated accounts have a hard limit on the number of active API keys allowed per organization. If the agent attempts to create a key while you are at your plan limit, the API will return a 403 error. You will need to delete unused keys via the agent before creating new ones to avoid these limits.
The agent uses the Retrieve DID Document action to resolve a Decentralized Identifier into a machine readable document. This document contains the public keys and service endpoints needed to verify a signature. When a user presents a credential, Ceven first pulls the DID Document of the issuer to ensure the cryptographic signature on the credential is valid. This process happens in milliseconds, allowing the agent to approve or deny access to a resource based on the proven identity of the user without requiring a centralized login or a password.
Yes, by using the Create Webhook action. The agent configures a listener URL that Dock Certs calls whenever a specific event occurs, such as a credential being issued or verified. Once the webhook is active, Dock Certs pushes the event data to your server, which can then trigger a Ceven workflow to perform downstream actions. For example, when a new certificate is issued, the agent can automatically send a congratulatory email to the user and update their profile in your CRM to reflect their new qualification.
Ceven acts as a conduit between your workflow and the Dock Certs API. While the agent processes the credential data to make decisions, it does not store the actual verifiable credentials in a permanent database. The data exists in the ephemeral context of the workflow run. If you need to keep a record of the verification, you should instruct the agent to push the verification result or the credential metadata to your own database or CRM. This architecture ensures that you maintain full control over the sensitive identity data of your users.
The Retrieve Credentials tool supports optional pagination. When the agent detects a large number of credentials, it automatically handles the cursor or page offset to ensure all records are captured. It will loop through the API responses until the full list is retrieved or until it finds the specific record you are searching for. This prevents the workflow from timing out or missing data when managing thousands of identity records, making it suitable for large scale institutional use cases where manual pagination would be impossible.

Alternatives to Dock Certs

Other tools that solve a similar problem. Ceven supports these too, so you can switch or run more than one at once.

Cheqd logoCheqdEvernym logoEvernym

Try Ceven on your stack

Plug Ceven on top of the tools you already run. Connect Dock Certs and the rest of your stack, describe the outcome, and its agents handle the work end to end, days of it in minutes.

Get started for free