AI marking
Ava's answers are marked as AI-generated in a machine-readable way (Art. 50(2) AI Act). This page explains how and lets you check a text.
Check a text
What is marked
Signed provenance information
Every answer that Ava generates with the language model carries a signed marker in JWS format (RFC 7515), signed with EdDSA (Ed25519, RFC 8037), on the page, in JSON responses, in the exports and in emails. It states that the content is AI-generated and gives the source type from the IPTC vocabulary, the name of the system (Ava), the provider, the time of generation, the SHA-256 checksum of the text and the address of this checking service, sometimes also the version of the instructions and the model. It contains nothing about people or conversations.
On the pages it sits on every element with Ava's text as the attributes ai-disclosure="ai-generated", data-digital-source-type and data-ai-provenance (the JWS). Source type: http://cv.iptc.org/newscodes/digitalsourcetype/trainedAlgorithmicMedia
Public key
Anyone can verify the signature without this checking service. The public keys are published as a JWK Set (RFC 7517) at the following address, the current one first. After a key change the earlier keys stay there, so older markers can still be verified: https://app.transformeducation.de/.well-known/ai-marking-jwks.json
The header of every marker carries the key's thumbprint (RFC 7638) as kid. Current key: r0nWJAeGnbkB4p1rOLCzTSG08-aXJYS5ysSeDNEZkaQ
{
"keys": [
{
"crv": "Ed25519",
"kty": "OKP",
"x": "5Ti6hKnw_c3lvecHcM2b7Awb-SFQtuiaBH98kasePMA",
"kid": "r0nWJAeGnbkB4p1rOLCzTSG08-aXJYS5ysSeDNEZkaQ",
"use": "sig",
"alg": "EdDSA"
}
]
}
Verify it yourself
- Split the marker at its two dots into header, payload and signature (each Base64url without padding).
- The header contains
algwith the valueEdDSAandkid; take the key with thiskidfrom the JWK Set. - Verify the Ed25519 signature over header, dot and payload (as ASCII) with the key's
xvalue. sha256holds the checksum of Ava's text as UTF-8, without the watermark and before it is rendered as Markdown. It therefore matches the text from an export, not necessarily what you copy from the page.
For example in Python with the cryptography package; verify raises InvalidSignature if the marker is not genuine:
import base64, json, urllib.request
from cryptography.hazmat.primitives.asymmetric.ed25519 import Ed25519PublicKey
def b64(s): return base64.urlsafe_b64decode(s + "=" * (-len(s) % 4))
token = "eyJ…"
head, body, sig = token.split(".")
keys = json.load(urllib.request.urlopen("https://app.transformeducation.de/.well-known/ai-marking-jwks.json"))["keys"]
key = next(k for k in keys if k["kid"] == json.loads(b64(head))["kid"])
Ed25519PublicKey.from_public_bytes(b64(key["x"])).verify(b64(sig), f"{head}.{body}".encode())
print(json.loads(b64(body)))
Invisible watermark in the text
Answers of 400 characters or more carry an invisible sequence of 19 Unicode variation selectors after the first word of the first and the last paragraph: U+FE00 to U+FE0F stand for the byte values 0 to 15, U+E0100 to U+E01EF for 16 to 255. The bytes: marker A7 7E, version 01, time of generation (4 bytes, Unix seconds), checksum (the first 4 bytes of SHA-256 over the letters and digits of the text in lower case after NFKC) and a signature (8 bytes of HMAC-SHA256).
A publicly verifiable signature would need 64 bytes, that is 75 instead of 19 invisible characters at each position. The watermark therefore carries an HMAC signature that only this checking service can confirm.
HTTP
Server responses with Ava's text carry the AI-Disclosure header following the draft draft-abaris-aicdh-00.
Limits
- The watermark survives copying and pasting, but not deliberate removal or retyping.
- The signed provenance information (EdDSA) can be verified publicly. The watermark in the text and older markers with the HS256 algorithm (
kidhs256-1) can only be confirmed by this checking service. - Short answers carry no watermark, only the signed information on the page.
- Fixed notices such as greetings and error messages are not AI output and are not marked.
- If the fixed pointer to the Help page stands below Ava's answer, it does not count towards the checksum: a copy that includes it checks as unchanged.
For programs
The same check as JSON, with a signed result (checksum of the text, checking service, time):
curl -s -X POST -H "Content-Type: application/json" -d '{"text": "…"}' "https://app.transformeducation.de/ki-kennzeichnung/?format=json"
The check result is signed with the same key. The public keys as JSON:
curl -s "https://app.transformeducation.de/.well-known/ai-marking-jwks.json"