Skip to content
Kennmarq.com, home
Menu

One API call marks your AI content for every market you serve

Pick a country to see what its law asks for, when it applies, and what we add.

Request early accessQuickstart
  • Covered 34
  • Partly covered 0
  • Planned 1
  • No rule found 164

World map of AI content labelling laws for images: 34 countries covered, 0 partly covered, 1 planned, 164 where we found no rule. Use the search to pick a country.

Coverage for images today

34of 35 countries with AI labelling rules for images

Elsewhere we found no rule that asks for labels; every file still carries a watermark and signed Content Credentials.

Next deadlines

  1. 2 Dec 2026EU AI Act, Article 50: AI systems already on the market
  2. 1 Jan 2027Utah · Digital Content Provenance Standards Act (HB 276)
  3. 1 Feb 2027Washington · AI content provenance law (HB 1170)
  4. 1 Mar 2027Vietnam · Law on AI and Decree 142/2026: Systems already running before then

Coming next

  1. Dec 2026Spoken notices in audio
  2. Jan 2027China's metadata label (GB 45438-2025)
  3. Mar 2027Text
  4. Jun 20273D models and scenes

Pick a country on the map for its laws and what we add.

Laws checked 4 Nov 2026. Not legal advice. Every country

How it works

One call, three marks, nothing to run

Send a file; get the same file back, marked. We run the signing keys, the watermark models and the time-stamp server, so you don't have to.

  1. 1

    Invisible watermark

    An ID hidden in the pixels or the sound: TrustMark in images, Video Seal in video, AudioSeal in audio. It leads back to the file's credential when platforms strip the metadata. In our published tests it survived JPEG at quality 50, a social-network-style resize and a resize to 25% on all 78 images.

  2. 2

    Signed Content Credentials

    A C2PA manifest saying the file was made or edited by AI, with your company, model and app, signed with our key and time-stamped by our own RFC 3161 server. Any C2PA reader can show it.

  3. 3

    Plain AI label

    IPTC DigitalSourceType in the file's XMP metadata: the field major platforms already read to label AI content.

Mark a picture
curl https://api.kennmarq.com/v1/mark \
  -H "Authorization: Bearer $KENNMARQ_API_KEY" \
  -F file=@image.png \
  -F source=created \
  -F provider="Acme Inc." \
  -F app_name="Acme Studio" -F app_version="2.1" \
  -F markets=eu,us-ca \
  -o image.marked.png
Response headers
HTTP/2 200
content-type: image/png
x-mark-id: mk_4Q8oT1n6mWc2fLr0aZ9eYb
x-watermark-id: 1a2b3c4d5e6f7081
x-markets: eu,us-ca
x-marks-used: 1
x-marks-limit: 1000

Marks say how a file was made and, if you send it, by which provider's AI system; never which person made it, or with which prompt. Credentials a file already carries, from an upstream model's API for example, are kept as an ingredient. 1,000 marks a month are free, with no card.

Guaranteed on every call

Every file we return is marked, logged and checkable

Both marks, or no file
Every picture and clip we return carries a signed, time-stamped credential and, unless you turn it off, an invisible watermark, both read back from the finished file before it leaves. If either fails, you get an error and the mark isn't counted. Songs always carry the credential, and the watermark whenever the sound can hold it; the credential says which.
California's five items
Send your company name, your AI system's name and version, and whether the file was made or edited: every mark then carries all five items of California's latent disclosure.
In the public log first
Every signature and time-stamp is in our public transparency log before the file reaches you, so none can be backdated or altered without it showing.
Free to check, for anyone
Anyone can check a picture at kennmarq.com/check, in their own browser: the picture never leaves their device.
A receipt for each law
Name the countries you serve (de, jp, us-ca…) and a call missing what their laws need is refused before anything is counted; each file gets a receipt of what it carries, signed when you ask for it.

Building with an AI coding agent?

Paste one prompt. Your agent adds the marks.

Cursor, Claude Code and other coding agents can read our docs as plain text, so this is all they need:

Prompt
Mark every AI image, video and audio file this app generates with Kennmarq.com before it's stored or shown. The API docs are at https://kennmarq.com/llms.txt. Send each file to POST https://api.kennmarq.com/v1/mark with the key from the KENNMARQ_API_KEY environment variable, and pass provider, app_name, app_version, source and markets=eu,us-ca. For deep fakes, realistic depictions of real people, places or events, also send deepfake=true: it adds the visible "AI" label. Keep only the marked file.

Then drop a result on kennmarq.com/check to see the marks. A standing rule for AGENTS.md or Cursor is in the coding agents guide.

Ways to use it

Works the way you build

A REST API for any language, SDKs for JavaScript and Python, and ComfyUI nodes. Every feature comes with every plan.

  • Cloud API

    Available

    Send a PNG, JPEG or WebP picture up to 25 MB and get it back marked, in seconds. Test and live keys, IP allowlists, usage headers, and SDKs for JavaScript and Python.

  • Safety check

    Available

    Screens a picture for sexual content with an apparent minor or a realistic face, the AI Act's Art. 5 bans, before you mark or publish it. Allow, flag or block, with published error rates.

  • Free public checker

    Available

    Anyone can check a file: both layers, and the credential found through the watermark when metadata was stripped. Pictures are checked in the browser; nothing is uploaded.

  • ComfyUI nodes

    Available

    Mark & Save nodes, in the ComfyUI Registry, that replace ComfyUI's Save nodes, so marks are added before the file is ever written. A free key works out of the box.

  • Local mode

    Available

    With the Python SDK, a picture's watermark and manifest are made on your own machine; only the manifest, about 13 KB and never pixels, comes to us to be signed and time-stamped.

  • Songs and clips

    Available

    Songs (MP3, WAV, M4A) with an inaudible AudioSeal mark, and clips (MP4 at up to 1080p: 2.5 minutes at 30 frames a second) with Video Seal in every frame, each signed and time-stamped. A song counts five marks per started minute, a clip five per started second.

Independent verification

Verify every mark yourself

Your users, platforms and regulators can check any mark, and our record of every signature, without asking us.

A public transparency log
Every signature and time-stamp, in an append-only log with signed roots, before the file reaches you.
A free checker
Anyone can check an image at kennmarq.com/check, in their browser: both marks, and all five California items.
A published robustness report
How often the watermark survives compression, resizing, crops and edits, with error bars, on the code the API runs: the report.
Open standards, open source
C2PA and IPTC are open standards; TrustMark, Video Seal and AudioSeal are open source. Your marks stay readable with anyone's tools.

Where your data lives

Your data stays in Switzerland and the EU

Three named sub-processors, encryption throughout, and files deleted once they're delivered.

AWS Zurich
Customer data is stored and marked in AWS's Zurich region. Requests pass through our API's front door in Frankfurt, in memory, and database backups are copied there.
Three sub-processors
AWS runs the service, Stripe takes payments, and Proton, in Switzerland, holds the email you send us. Time-stamps, the checker and the transparency log run on our own infrastructure.
Files aren't kept
Pictures and songs are marked in memory and never stored. Uploads are deleted once used, within the hour, and marked clips after the day they wait for you to download them. Our records keep hashes, never contents or file names.
Encryption and keys
Signing keys live in AWS KMS and never leave it. Your API keys are stored only as hashes and shown once.

Security and control

The controls your security review asks for, in every plan

Organisations and roles
Owner, admin, developer, billing and viewer, with invitations by email.
Test and live keys
Separate keys and separate allowances per environment, with scopes, so a key can only do its job.
IP allowlists
Limit any key to your servers' IPv4 and IPv6 ranges.
Tamper-evident audit log
Every sign-in, member, key and setting change, hash-chained so edits show, exportable as CSV or JSON.

Read our trust center and status page. Enterprise adds single sign-on, your own signing identity and private deployment. Talk to sales@kennmarq.com.

Start free: 1,000 marks a month, every feature.

Paid plans from USD 9 a month add volume, speed and support.

Request early accessSee pricing