CertSeal for AI agents

CertSeal issues and manages verifiable digital certificates, letting an organization batch-generate credentials for things like course completions or event attendance. 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.

DocumentsAPI keyMCP + REST
AUDIT LOG · CERTSEALPOLICY: acme-support
09:41:07 · claude · u_8f2read
certseal.list_batches
List Batches✓ allowed · 212ms
09:41:08 · claude · u_8f2read
certseal.get_batch
Get Batch✓ allowed · 164ms
09:41:09 · claude · u_8f2write
certseal.create_batch
Create Batch✓ approved · approved by user
09:41:12 · claude · u_8f2destructive
certseal.delete_recipient
Delete Recipient✕ blocked · policy: deny
EVERY CERTSEAL CALL, ON THE RECORD
01 · USE CASES

What agents do in CertSeal.

01

Issue a batch of certificates

Issue certificates to a batch of recipients once a course or event has wrapped up.

02

Look up a recipient's certificate

Look up a specific recipient's certificate to confirm it was issued correctly.

03

Confirm before deleting a recipient

Confirm before deleting a recipient record, since their issued certificates lose that reference.

02 · ACTIONS

21 CertSeal actions, graded by risk.

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

read

10

Look things up. Allowed by default.

  • certseal.get_batch
    Get Batch
  • certseal.list_batches
    List Batches
  • certseal.list_designs
    List Designs
  • certseal.get_recipient
    Get Recipient
  • certseal.get_certificate
    Get Certificate
  • certseal.list_recipients
    List Recipients
  • certseal.get_current_workspace
    Get Current Workspace
  • certseal.get_webhook_subscription
    Get Webhook Subscription
  • certseal.list_webhook_subscriptions
    List Webhook Subscriptions
  • certseal.test_webhook_subscription
    Test Webhook Subscription

write

9

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

  • certseal.create_batch
    Create Batch
  • certseal.update_recipient
    Update Recipient
  • certseal.send_certificate_emails
    Send Certificate Emails
  • certseal.create_webhook_subscription
    Create Webhook Subscription
  • certseal.send_recipient_certificate_email
    Send Recipient Certificate Email
  • certseal.issue_certificates
    Issue Certificates
  • certseal.set_batch_archived
    Set Batch Archived State
  • certseal.issue_and_send_certificates
    Issue and Send Certificates
  • certseal.rotate_webhook_signing_secret
    Rotate Webhook Signing Secret

destructive

2

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

  • certseal.delete_recipient
    Delete Recipient
  • certseal.delete_webhook_subscription
    Delete Webhook Subscription
03 · HOW IT WORKS

CertSeal in three steps.

  1. 01Your users connect CertSealThey add their CertSeal api key on Arc0 Connect, under your brand. It goes straight into the vault.
  2. 02You set the rulesReads run, writes like “create Batch” can wait for the user, and “delete Recipient” can be denied outright.
  3. 03Any agent can actYour agent calls CertSeal 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('certseal', {
  read: 'allow',
  write: 'ask',        // create_batch
  destructive: 'deny',  // delete_recipient
})

# 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 CertSeal connects.

Users add their CertSeal 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 CertSeal 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 CertSeal from any agent.

Claude
ChatGPT
Cursor
Codex
VS Code
OpenAI Agents SDK
Claude Agent SDK
Vercel AI SDK
Mastra
LangGraph
07 · FAQ

CertSeal and Arc0, answered.

Q01

Can I use CertSeal with Claude, ChatGPT or Cursor?

Yes. Connect CertSeal 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 CertSeal actions you allow.

Q02

How do users connect CertSeal?

Users add their CertSeal 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 CertSeal actions can my agent take?

21 in total: 10 read, 9 write and 2 destructive, such as “create Batch”. Your policies decide which of them each agent may call.

Q04

Can I stop my agent from deleting things in CertSeal?

Yes. Actions like “delete Recipient” 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 CertSeal too?

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

Get started

Plug CertSeal into your agent.

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

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