Evaluate Ankorith in your own systems

1. Sign in

Open sign-in and use Google, Microsoft, GitHub, a one-time e-mail link or a passkey. No passwords are stored.

2. Verify your domain

In your account, enter the domain your company publishes under. Prove control of it with one of:

# DNS TXT record
_ankorith.yourcompany.com   TXT   "ankorith-verify=<token>"

# or a file on your website
https://yourcompany.com/.well-known/ankorith.txt   →   ankorith-verify=<token>

The token is valid for 7 days. After verification, your seals carry your domain as the verified issuer, and the verification itself is recorded in the public log.

3. Create an API key

The primary key is shown once after domain verification. For each system (CMS, DAM, a generator pipeline) create a named sub-key in your account — or through the API with the primary key — so that keys can be revoked one by one. We store only fingerprints of keys; a key you lose cannot be shown again, only replaced.

curl -X POST https://ankorith.com/seal/api/keys \
  -H "Authorization: Bearer $PRIMARY_KEY" -H "Content-Type: application/json" \
  -d '{"name":"cms-production"}'

4. Your first seal

You send only the SHA-256 fingerprint of the file and your declaration (photo, human, ai-edited or ai-generated). The file stays with you.

curl

SHA=$(shasum -a 256 banner.jpg | cut -d' ' -f1)
curl -X POST https://ankorith.com/seal/api/bulk \
  -H "Authorization: Bearer $ANKORITH_KEY" -H "Content-Type: application/json" \
  -d "{\"items\":[{\"sha256\":\"$SHA\",\"declaration\":\"ai-generated\",\"tool\":\"Your model\",\"name\":\"Banner 01\"}]}"

Node.js (18 or newer)

import { createHash } from "node:crypto";
import { readFile } from "node:fs/promises";

const sha256 = createHash("sha256").update(await readFile("banner.jpg")).digest("hex");
const res = await fetch("https://ankorith.com/seal/api/bulk", {
  method: "POST",
  headers: { Authorization: `Bearer ${process.env.ANKORITH_KEY}`, "Content-Type": "application/json" },
  body: JSON.stringify({ items: [{ sha256, declaration: "ai-generated", tool: "Your model", name: "Banner 01" }] }),
});
const { results } = await res.json();
console.log(results[0].verifyUrl ?? results[0].error);

Python

import hashlib, os, pathlib, requests

sha256 = hashlib.sha256(pathlib.Path("banner.jpg").read_bytes()).hexdigest()
r = requests.post("https://ankorith.com/seal/api/bulk",
                  headers={"Authorization": "Bearer " + os.environ["ANKORITH_KEY"]},
                  json={"items": [{"sha256": sha256, "declaration": "ai-generated",
                                   "tool": "Your model", "name": "Banner 01"}]})
item = r.json()["results"][0]
print(item.get("verifyUrl") or item.get("error"))

Each result carries the seal id, its position in the public log and a verifyUrl. Up to 100 items per request; a failing item does not stop the others. For a machine-readable label inside JPEG/PNG files, appearance matching and change localisation, use the reserve → embed → issue flow described in the API documentation.

5. Verify

Drop the file on ankorith.com/seal — the fingerprint is computed in the browser and the page checks the signed public log itself. Or verify from your systems:

curl "https://ankorith.com/seal/api/verify?sha256=$SHA"

6. Optional: webhooks and usage

Register an HTTPS endpoint to receive a notification, signed with HMAC-SHA256, for every issued seal. No server ready yet? Use the built-in test receiver described in the API documentation. GET /seal/api/usage returns seals per month and per key.