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.
What agents do in CertSeal.
Issue a batch of certificates
Issue certificates to a batch of recipients once a course or event has wrapped up.
Look up a recipient's certificate
Look up a specific recipient's certificate to confirm it was issued correctly.
Confirm before deleting a recipient
Confirm before deleting a recipient record, since their issued certificates lose that reference.
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
10Look things up. Allowed by default.
- certseal.get_batchGet Batch
- certseal.list_batchesList Batches
- certseal.list_designsList Designs
- certseal.get_recipientGet Recipient
- certseal.get_certificateGet Certificate
- certseal.list_recipientsList Recipients
- certseal.get_current_workspaceGet Current Workspace
- certseal.get_webhook_subscriptionGet Webhook Subscription
- certseal.list_webhook_subscriptionsList Webhook Subscriptions
- certseal.test_webhook_subscriptionTest Webhook Subscription
write
9Create and change things. Allow, or ask the user first.
- certseal.create_batchCreate Batch
- certseal.update_recipientUpdate Recipient
- certseal.send_certificate_emailsSend Certificate Emails
- certseal.create_webhook_subscriptionCreate Webhook Subscription
- certseal.send_recipient_certificate_emailSend Recipient Certificate Email
- certseal.issue_certificatesIssue Certificates
- certseal.set_batch_archivedSet Batch Archived State
- certseal.issue_and_send_certificatesIssue and Send Certificates
- certseal.rotate_webhook_signing_secretRotate Webhook Signing Secret
destructive
2Delete, cancel or archive. Ask first, or deny outright.
- certseal.delete_recipientDelete Recipient
- certseal.delete_webhook_subscriptionDelete Webhook Subscription
CertSeal in three steps.
- 01Your users connect CertSealThey add their CertSeal api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “create Batch” can wait for the user, and “delete Recipient” can be denied outright.
- 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.
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
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
Use CertSeal from any agent.
CertSeal and Arc0, answered.
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.
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.
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.
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.
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.
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