API REFERENCE
Create verifiable proofs from AI interactions.
https://sealison.com
All requests require an API key.
x-api-key: marble_demo_2026
This is a public demo key for testing.
For production usage, request a dedicated key.
POST /api/prove
Creates a cryptographic proof of an AI interaction.
The content is never stored.
SEALISON canonicalizes and hashes the payload deterministically.
POST /api/prove
{
"mode": "hash-only",
"payload": {
"schema_version": "1",
"kind": "ai_interaction",
"output": "Refund of $100 processed",
"timestamp": "2026-04-15T10:00:00Z"
}
}The content is stored and displayed on the proof page.
POST /api/prove
{
"mode": "full",
"content": "Refund of $100 processed"
}{
"proof_id": "mrb_73c50d3fa6e22d7e",
"url": "https://sealison.com/p/mrb_73c50d3fa6e22d7e"
}The proof URL can be shared or verified anytime.
Verification does not require the API.
Open the proof URL and paste the original content.
The hash is recomputed in the browser and compared.
No server trust required.
{"error": "Missing x-api-key header"}{"error": "Invalid API key"}{"error": "Invalid payload"}{"error": "Internal server error"}Deterministic hashing
The payload is canonicalized before hashing. The same input always produces the same hash.
Tamper evidence
Any modification to the content produces a different hash. This breaks verification.
Independent verification
Proofs can be verified without access to the server. Integrity does not depend on SEALISON.
HASH-ONLY
Content is sensitive (PII, financial, medical)
Cannot send raw data to external services
Need audit-grade integrity guarantees
FULL
Want a human-readable proof page
Content is not sensitive
Testing or demonstrating the system
Logs show what happened.
Proofs show that it hasn’t changed.