CertSeal

@CertSeal list all recipients in batch batch_abc123 who haven't opened their certificate yet

Found 47 recipients in batch 'Q2 2024 Training Completion'. 12 recipients have not yet opened their certificates: Emma Chen (issued 2024-03-15), Marcus Rodriguez (issued 2024-03-14), Sarah Kim (issued 2024-03-13)... The batch contains 47 total certificates issued between March 12-18. All unopened certificates were delivered successfully via email; no bounce-backs recorded.

This example shows read-only batch inspection. The MCP can filter recipients by status (opened, unopened, revoked) but cannot determine why a recipient hasn't opened their certificate—email delivery confirmation doesn't guarantee the recipient saw or clicked the link. Requires read scope on the workspace.

@CertSeal create a new batch using design_xyz789 for our March workshop graduates, then issue certificates to the 8 people in graduates.csv

Created batch 'March 2024 Workshop Graduates' (batch_def456) using design 'Professional Development Certificate'. Issued 8 certificates successfully: certificates are now live and delivery emails sent to all recipients. Each certificate includes the recipient's name, completion date, and workshop title as specified in your CSV. Batch consumes 1 of your 5 available batch slots; 8 certificates deducted from your monthly quota of 500.

This write operation creates a persistent batch and immediately issues certificates, consuming quota and batch slots. If your plan's batch limit is reached, creation fails and no certificates are issued—check available slots with Get Current Workspace first. Certificate issuance cannot be undone; use Delete Recipient only for compliance removal, not mistakes.

@CertSeal check which certificate designs have been used most in the last 90 days and summarize what makes the top design effective

Your workspace has issued 1,247 certificates across 6 designs in the last 90 days. The 'Employee Recognition Award' design (design_ghi012) accounts for 64% of all issuance (798 certificates across 23 batches). This design uses a formal border, company logo placement in the top-right, and includes three custom variables: recipient name, achievement category, and manager signature. Its high usage suggests it serves as your general-purpose recognition template, flexible enough for multiple award types while maintaining brand consistency.

This synthesis example combines batch and design data with AI reasoning to surface usage patterns. The MCP provides raw issuance counts and design metadata; the AI interprets what makes a design 'effective' based on adoption signals. Accuracy depends on having sufficient historical data—new workspaces with <30 days of activity won't yield meaningful trends.

When CertSeal wins for event credential workflows

A 6-person event ops team running a 400-attendee conference needs to issue completion certificates and speaker badges in real time as sessions close. CertSeal's batch-and-recipient model fits this perfectly: create one batch per track, wire the webhook subscription to your registration platform, and trigger certificate generation when an attendee checks in or a session ends. The 21-tool surface gives you fine control over design variables and deletion (useful when someone requests removal under GDPR). The API key auth keeps setup simple for non-technical event staff. If your event is under 1,000 attendees and you need same-day turnaround, CertSeal handles the templating and delivery without custom PDF rendering. Book a demo if you're issuing more than 5,000 credentials per quarter.

CertSeal for regulated training certificate workflows

A 12-person L&D team at a healthcare SaaS company must issue and archive training certificates to meet SOC 2 audit requirements. CertSeal's persistent batch model and recipient lookup tools let you prove certificate issuance years later without maintaining your own certificate database. Create one batch per course, issue certificates via the API when learners pass the final quiz, and store the certificate ID in your LMS. The webhook subscription notifies your compliance dashboard when certificates are viewed or shared. The delete-recipient tool exists but burns quota permanently, so use it only for true data-deletion requests. If you're issuing fewer than 500 certificates per month and need audit-trail proof of delivery, CertSeal's architecture is purpose-built for this. Skip it if you need sub-second issuance or plan to issue more than 10,000 certificates per year.

When CertSeal handles partner credential distribution

A 3-person partner success team at a B2B platform runs a quarterly certification program for resellers and needs to issue branded credentials that partners can share on LinkedIn. CertSeal's design-and-template pairing lets you maintain brand consistency across cohorts while personalizing recipient names and completion dates. The get-certificate tool supports public share tokens, so partners can link directly to a hosted viewer page without you building a custom portal. Webhook subscriptions let you track which partners are actively promoting their credentials. The 21-tool count signals depth, but most teams only touch 6-8 tools in practice. If you're certifying fewer than 200 partners per quarter and want zero infrastructure overhead, CertSeal delivers. Move to a custom solution if you need white-label domains or plan to issue more than 2,000 certificates annually.