QUICKSTART

Get started in under a minute.

No setup. No account. No SDK required.

Hash the AI interaction in your own client, then send only the hash.

Clients compute the canonical hash locally and send only payload_hash to Sealison. Use SHA-256 over the canonical JSON of your payload per the Sealison canonicalization (UTF-8, Unicode NFC, CRLF/CR normalized to LF, deterministic key order; no trimming; no whitespace collapse; no BOM stripping).

The server never receives the original content.

TRY IT — NO API KEY

curl -X POST https://sealison.com/api/demo/prove \
  -H "Content-Type: application/json" \
  -d '{
    "payload_hash": "9f86d081884c7d659a2feaa0c55ad015a3bf4f1b2b0b822cd15d6c15b0f00a08"
  }'

→ Returns a proof URL you can share or verify anytime. Public demo: rate-limited to 5 requests per IP per hour.

PRODUCTION — WITH AN API KEY

curl -X POST https://sealison.com/api/prove \
  -H "Content-Type: application/json" \
  -H "x-api-key: ck_live_a1b2c3d4" \
  -d '{
    "payload_hash": "9f86d081884c7d659a2feaa0c55ad015a3bf4f1b2b0b822cd15d6c15b0f00a08"
  }'

→ Higher volumes, custom retention. For pilot or integration questions, email [email protected].

Any body containing payload, content, or mode:"full" is rejected with 400 PAYLOAD_REJECTED.

The interaction is turned into a cryptographic proof.

A SHA-256 hash is computed, sealed in a chain, and signed.

{
  "proof_id": "mrb_73c50d3fa6e22d7e",
  "url": "https://sealison.com/p/mrb_73c50d3fa6e22d7e"
}

Open the proof URL and paste the original content.

The hash is recomputed in your browser and compared.

Verification runs client-side from the exported proof bundle. Public CLI verifier planned.

https://sealison.com/p/mrb_73c50d3fa6e22d7e

→ Paste content → "Verify hash"
→ ▲ Hash matches. Content has not been modified.

What you get

Ready to integrate?

Logs are claims.
Proof is verifiable.