
Dock Certs
Applicants ask about their certification status. Partners need to verify a credential. Your AI agent handles it all by interfacing with Dock Certs in real-time, issuing blockchain-anchored credentials, checking revocation registries, and resolving DIDs without manual steps.




From issuance to verification and revocation checks, your AI agent operates Dock Certs' full credential infrastructure directly within customer conversations.
Dock Certs
How organizations issuing digital certificates use AI agents to streamline verification, support credential holders, and maintain compliance automatically.
A recruiter needs to verify a candidate's professional certification. They provide the credential ID to your AI Agent, which calls Dock Certs' verify endpoint, checks the cryptographic signature and revocation status, and returns a clear pass or fail result. The recruiter confirms the credential is valid in under a minute. No emails to the issuing body, no waiting days for manual confirmation.
A graduate needs a copy of their digital certificate for a job application. They message your AI Agent with their name or student ID. The agent searches Dock Certs' credential list, finds the matching record, and shares the credential details including issuance date and issuer DID. The graduate gets what they need at midnight on a Sunday, no admin office hours required.
An auditor asks how many active revocation registries your organization maintains and which credentials are linked to each. Your AI Agent queries Dock Certs for the registry list, cross-references with issued credentials, and presents a summary. The auditor gets structured compliance data through a simple chat. Your compliance team saves hours of manual report assembly.

Dock Certs
FAQs
The agent sends the credential or presentation to Dock Certs' verification endpoint, which checks the cryptographic proof against the issuer's public key on the Dock blockchain and confirms it has not been revoked. The result is a boolean 'verified' status along with any error details. The entire check takes seconds and requires no manual review of signatures or blockchain records.
The agent can retrieve, verify, and manage existing credentials. Issuance workflows typically involve your backend systems creating the credential through Dock Certs' API with the appropriate DID and schema. The agent supports the verification and lookup side of the lifecycle, keeping issuance within your controlled processes.
Tars accesses credential metadata, DID documents, and revocation registry information through Dock Certs' API. Personally identifiable information embedded in credentials is not stored by Tars. Dock itself never stores credential content on the blockchain. Data flows through the conversation and is not persisted.
Yes. The agent knows that a DID is a decentralized identifier representing an entity, while a verifiable credential is a signed claim about that entity. When someone asks to 'check a certificate,' the agent resolves whether they need credential verification or DID resolution and calls the appropriate Dock Certs endpoint.
Yes. The verification endpoint automatically checks the credential's revocation status against the linked registry on the Dock blockchain. If a credential was revoked after issuance, the verification response will indicate it is no longer valid, and the agent communicates this clearly to the person asking.
The Dock Certs console requires login credentials, navigation through multiple screens, and technical understanding of DIDs and registries. With Tars, anyone can ask a question in plain language, and the agent handles the API calls behind the scenes. Recruiters, students, or auditors get answers without ever seeing a dashboard.
If Dock Certs' API returns an error due to blockchain connectivity issues, the agent informs the user that verification is temporarily unavailable and suggests retrying shortly. It does not return a false positive or negative. Reliability depends on Dock's infrastructure uptime, which uses a Substrate-based blockchain designed for high availability.
Yes. The verification endpoint works for any credential issued on the Dock network, regardless of the issuer. The agent resolves the issuer's DID, verifies the cryptographic signature, and checks the revocation registry. Cross-organization verification is a core feature of Dock's decentralized identity model.
Don't limit your AI Agent to basic conversations. Watch how to configure and add powerful tools making your agent smarter and more functional.

Privacy & Security
At Tars, we take privacy and security very seriously. We are compliant with GDPR, ISO, SOC 2, and HIPAA.