Get started

Certifier for AI agents

Certifier lets organizations design, issue, and send digital certificates and credentials at scale, for things like course completions or membership badges. 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 CertifierSee the 9 actions ↓
DocumentsAPI keyMCP + RESTcertifier.io
AUDIT LOG · CERTIFIERPOLICY: acme-support
09:41:07 · claude · u_8f2read
certifier.list_groups
List Groups✓ allowed · 212ms
09:41:08 · claude · u_8f2read
certifier.list_designs
List Designs✓ allowed · 164ms
09:41:09 · claude · u_8f2write
certifier.create_issue_send_credential
Create, issue, and send credential✓ approved · approved by user
EVERY CERTIFIER CALL, ON THE RECORD
01 · USE CASES

What agents do in Certifier.

01

Issue and send a credential

Issue a credential to a recipient and send it directly to their inbox once earned.

02

Search issued credentials

Search existing credentials by recipient name to confirm one was already issued.

03

Check credential interactions

List a credential's interactions, such as views or shares, before reporting on program reach.

02 · ACTIONS

9 Certifier actions, graded by risk.

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

read

7

Look things up. Allowed by default.

  • certifier.list_groups
    List Groups
  • certifier.list_designs
    List Designs
  • certifier.list_attributes
    List Attributes
  • certifier.list_credentials
    List Credentials
  • certifier.search_credentials
    Search Credentials
  • certifier.list_email_templates
    List Email Templates
  • certifier.list_credential_interactions
    List Credential Interactions

write

2

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

  • certifier.send_credential
    Send a Credential
  • certifier.create_issue_send_credential
    Create, issue, and send credential

destructive

0

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

  • No destructive actions.
03 · HOW IT WORKS

Certifier in three steps.

  1. 01Your users connect CertifierThey add their Certifier api key on Arc0 Connect, under your brand. It goes straight into the vault.
  2. 02You set the rulesReads run, and writes like “create, issue, and send credential” can wait for the user to approve.
  3. 03Any agent can actYour agent calls Certifier 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('certifier', {
  read: 'allow',
  write: 'ask',        // create_issue_send_credential
  destructive: 'deny',  
})

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

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

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

More documents apps.

Google Docs43 actionsActiveMerge13 actionsAirparser10 actionsAlgodocs3 actionsDocuSign338 actionsSharePoint Graph162 actionsSharePoint105 actionsDocumenso77 actions
ALL DOCUMENTS APPS →
07 · FAQ

Certifier and Arc0, answered.

Q01

Can I use Certifier with Claude, ChatGPT or Cursor?

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

Q02

How do users connect Certifier?

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

9 in total: 7 read, 2 write and 0 destructive, such as “create, issue, and send credential”. Your policies decide which of them each agent may call.

Q04

Can I make my agent read-only in Certifier?

Yes. Allow read actions and deny writes in the Certifier policy. Your agent can still look things up, and any write it attempts is blocked and logged.

Q05

Can my own backend call Certifier too?

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

Get started

Plug Certifier into your agent.

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

Connect CertifierBrowse all apps →

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