Developers

Seal and verify from anywhere in your stack.

A CLI, a GitHub Action, an HTTP API, and SDKs, all open source, Apache-2.0. Seal any file behind your API key or your own instance; anyone verifies publicly.

sealbot, the CLI

The core tool for humans and scripts alike. Seal, anchor, and verify anything, PDFs, images, XML, email, or any file, from your terminal. sealbot seal picks the right form for each file type. Point it at the hosted service or your own instance with --api.

sealbot on GitHub CLI reference

$ sealbot seal report.pdf
$ sealbot seal photo.jpg
$ sealbot verify report.pdf
$ sealbot seal *.pdf --api https://seal.acme.internal

Verification is public. Anyone re-hashes the file and checks the signature, the transparency log, and the blockchain anchor.

In your pipeline

Seal release artefacts, reports, or generated PDFs automatically with the GitHub Action. Every build ships documents anyone can prove are genuine.

- uses: letsseal/sealbot-action@v1
  with:
    mode: seal
    files: dist/**/*.pdf
    # LETSSEAL_TOKEN in repo secrets

API & SDKs

JavaScript / TypeScript

npm i @letsseal/sdk

Python

pip install letsseal

go get github.com/letsseal/go-letsseal

HTTP

curl -F file=@x app.letsseal.org/api/v1/verify

The verify endpoint is public and unauthenticated by design. The seal endpoint holds signing keys and is protected. On the hosted service it’s tied to your account; when self-hosting it never leaves your network.

Everything is open

sealbot, the SDKs, the web app, and the signing service are all open source under the letsseal organisation on GitHub. Read it, fork it, run it, contribute back.

github.com/letsseal How the project stays open Get started