Sanaf AI
Start free
Signatures

CertSeal, worked by an AI employee

Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your CertSeal account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.

  • Signatures
  • Connects with a key
  • 21 ready-made tools
  • Asked in Slack or Teams
At work

An illustration of how the conversation reads, not a transcript from a client account.

What CertSeal is

CertSeal provides APIs for issuing and managing verifiable digital certificates, recipients, batches, designs, and webhook subscriptions.

You paste in a key from your own CertSeal account. It is kept encrypted, and you can withdraw it from inside CertSeal whenever you like.

How a run works

One message in, the work done in CertSeal.

  1. 01

    You ask

    You message your AI employee in the chat your team already has open, in one sentence, in your own words.

  2. 02

    It works out the step

    It decides what the job needs in CertSeal. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own CertSeal account, inside the access you granted it, doing the thing you asked for.

  4. 04

    It reports back

    It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.

21 tools it already has

What it can do in CertSeal

These are the ready-made tools your AI employee already has in CertSeal. It is not limited to them, but it never has to be taught these.

  • Create BatchCreate a persistent certificate batch from an existing CertSeal design and optional email template. This consumes a batch slot and can fail when the plan batch limit is reached; de
  • Create Webhook SubscriptionCreate a persistent webhook subscription for selected certificate events. The response contains a whsec signing secret exactly once; capture it immediately and store it securely be
  • Delete RecipientPermanently delete an issued recipient from an active batch. This cannot be undone, does not refund certificate quota, and permanently burns the certificate ID. Use only when perma
  • Delete Webhook SubscriptionPermanently delete a webhook subscription and stop future deliveries. This cannot be undone; create a new subscription to resume events.
  • Get BatchGet one active or archived certificate batch by ID.
  • Get CertificateLook up an issued certificate using either its human-readable certificate ID or its public-viewer share token, and return its recipient, batch, design, and resolved variables. Prov
  • Get Current WorkspaceVerify the connected CertSeal API key and return the workspace ID and username it belongs to. Use this to confirm account context before creating or changing resources.
  • Get RecipientGet one issued certificate recipient record by batch ID and recipient ID.
  • Get Webhook SubscriptionGet one webhook subscription by ID. This does not reveal the signing secret; it returns only the stored secret tail.
  • Issue and Send CertificatesAtomically issue certificates for 1-100 recipients and queue email delivery for every created certificate. This irreversible external side effect requires every recipient to have a
  • Issue CertificatesAtomically issue certificates without sending email for 1-100 recipients in one active batch. Each recipient permanently consumes one certificate quota unit even if later deleted;
  • List BatchesReturn one newest-first page of certificate batches in the connected workspace, optionally filtered by archive state.
  • List DesignsReturn one newest-first page of reusable certificate designs. Designs are read-only through the API and must be authored in the CertSeal web app.
  • List RecipientsReturn one page of issued certificate recipients in a batch, optionally filtered by email delivery status.
  • List Webhook SubscriptionsReturn one newest-first page of webhook subscriptions. Stored signing secrets are never returned; secrettail is only a non-sensitive identifier.
  • Rotate Webhook Signing SecretImmediately invalidate a webhook subscription's current signing secret and replace it. The new whsec secret is returned exactly once; capture and deploy it immediately or webhook v
  • Send Certificate EmailsSequentially queue real certificate emails for 1-25 existing recipients in one active batch. Each queued email is irreversible. Processing stops after the first failed or unknown a
  • Send Recipient Certificate EmailQueue asynchronous certificate email delivery to one recipient. This causes an external email side effect and requires a recipient email, a batch email template, and configured mai
  • Set Batch Archived StateIdempotently archive or unarchive a batch. Archiving freezes recipient create, update, delete, and send operations but preserves existing certificate URLs; unarchiving re-enables t
  • Test Webhook SubscriptionEnqueue one synthetic signed event through CertSeal's normal webhook dispatcher. This causes a real external delivery to the subscription URL; it does not only validate the subscri
  • Update RecipientPartially update an issued certificate recipient. Only supplied fields change, while an explicit null clears an optional field; changing certificateid must remain globally unique.
Access, and who is in charge of it

You stay the boss of your CertSeal account.

Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.

How we handle your data
  • It signs in to your own CertSeal account. You are not moving anything into ours.
  • You grant access one app at a time, and you can take it back the same way.
  • Everything it does in CertSeal is written down, with what it did and when.
  • Anything you tell it to check with you first, it checks with you first.
Other apps in the same corner of the business

It works in CertSeal and the rest of your software in the same job

A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.

See every app

Questions people ask about CertSeal

Can an AI employee really work inside CertSeal?
Yes. It signs in to your own CertSeal account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
Do I have to move anything out of CertSeal?
No. Nothing moves and nothing is replaced. Your records stay in CertSeal, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
How does it get into my CertSeal account?
You paste in a key from your own CertSeal account. It is kept encrypted, and you can withdraw it from inside CertSeal whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
What can it actually do in CertSeal?
It has 21 ready-made tools in CertSeal today, among them Create Batch, Create Webhook Subscription and Delete Recipient. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use CertSeal and the rest of my software in the same job?
Yes, and that is usually the point. Reading a message in one app, checking a record in CertSeal and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
Who decides what it is allowed to do in CertSeal?
You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in CertSeal is written down with what it did and when.