Get started

Dock Certs for AI agents

Dock Certs lets organizations issue, manage, and verify digital credentials and decentralized identities, so a credential can be checked instantly without contacting the issuer. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.

Connect Dock CertsSee the 15 actions ↓
Security and identityAPI keyMCP + RESTdock.io
AUDIT LOG · DOCK CERTSPOLICY: acme-support
09:41:07 · claude · u_8f2read
dock_certs.verify
Verify Credential or Presentation✓ allowed · 212ms
09:41:08 · claude · u_8f2read
dock_certs.retrieve_did
Retrieve DID Document✓ allowed · 164ms
09:41:09 · claude · u_8f2write
dock_certs.create_api_key
Create API Key✓ approved · approved by user
09:41:12 · claude · u_8f2destructive
dock_certs.delete_tag
Delete Tag✕ blocked · policy: deny
EVERY DOCK CERTS CALL, ON THE RECORD
01 · USE CASES

What agents do in Dock Certs.

01

Verify a submitted credential

Verify a credential or presentation a user submitted before granting them access to a program.

02

Look up a DID document

Retrieve a decentralized identity document to confirm a holder's public keys before trusting a claim.

03

Approve before revoking a credential

Route a credential deletion through approval, since revoking it removes the holder's ability to prove that claim.

02 · ACTIONS

15 Dock Certs actions, graded by risk.

Every Dock Certs action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.

read

9

Look things up. Allowed by default.

  • dock_certs.verify
    Verify Credential or Presentation
  • dock_certs.retrieve_did
    Retrieve DID Document
  • dock_certs.retrieve_api_key
    Retrieve API Key
  • dock_certs.retrieve_webhook
    Retrieve Webhook
  • dock_certs.retrieve_api_keys
    Retrieve API Keys
  • dock_certs.retrieve_webhooks
    Retrieve Webhooks
  • dock_certs.retrieve_credential
    Retrieve Credential
  • dock_certs.retrieve_registries
    Retrieve Revocation Registries
  • dock_certs.retrieve_credentials
    Retrieve Credentials

write

2

Create and change things. Allow, or ask the user first.

  • dock_certs.create_api_key
    Create API Key
  • dock_certs.create_webhook
    Create Webhook

destructive

4

Delete, cancel or archive. Ask first, or deny outright.

  • dock_certs.delete_tag
    Delete Tag
  • dock_certs.delete_api_key
    Delete API Key
  • dock_certs.delete_webhook
    Delete Webhook
  • dock_certs.delete_credential
    Delete Credential
03 · HOW IT WORKS

Dock Certs in three steps.

  1. 01Your users connect Dock CertsThey add their Dock Certs api key on Arc0 Connect, under your brand. It goes straight into the vault.
  2. 02You set the rulesReads run, writes like “create API Key” can wait for the user, and “delete Tag” can be denied outright.
  3. 03Any agent can actYour agent calls Dock Certs through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
POLICY.TS
await arc0.policies.set('dock_certs', {
  read: 'allow',
  write: 'ask',        // create_api_key
  destructive: 'deny',  // delete_tag
})

# Claude Code: the same connection, one URL
$ claude mcp add --transport http arc0 \
    https://mcp.arc0.ai/u/u_8f2
04 · AUTH AND DATA

How Dock Certs connects.

Users add their Dock Certs api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

The same Dock Certs connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →

AUTH
API key
CREDENTIALS
Per-tenant encrypted vault
MODEL SEES
Results only, never credentials
AUDIT LOG
Every call, on every plan
05 · WORKS WITH

Use Dock Certs from any agent.

Claude
ChatGPT
Cursor
Codex
VS Code
OpenAI Agents SDK
Claude Agent SDK
Vercel AI SDK
Mastra
LangGraph
06 · RELATED

More security and identity apps.

1Password6 actionsAbuseIPDB6 actionsAnonyflow5 actionsDnsfilter170 actionsBorneo153 actionsDigicert101 actionsParadym69 actionsPersona69 actions
ALL SECURITY AND IDENTITY APPS →
07 · FAQ

Dock Certs and Arc0, answered.

Q01

Can I use Dock Certs with Claude, ChatGPT or Cursor?

Yes. Connect Dock Certs to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Dock Certs actions you allow.

Q02

How do users connect Dock Certs?

Users add their Dock Certs api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

Q03

Which Dock Certs actions can my agent take?

15 in total: 9 read, 2 write and 4 destructive, such as “create API Key”. Your policies decide which of them each agent may call.

Q04

Can I stop my agent from deleting things in Dock Certs?

Yes. Actions like “delete Tag” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.

Q05

Can my own backend call Dock Certs too?

Yes. The same Dock Certs connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.

Get started

Plug Dock Certs into your agent.

Your users connect Dock Certs once, under your brand. Your agent gets 15 actions behind your policies, with every call on the record.

Connect Dock CertsBrowse all apps →

Free to build · MCP + REST · Audit log on every plan