Quickstart

Ship verifiable provenance in minutes. Pick the conformance level you can support, pick your platform, copy the block. Levels 1 and 2 are pure copy-paste today. Level 3 signing uses reference tooling that is rolling out.

The spec → Use cases → Verify a claim →

The whole thing, in four steps

Pick a conformance level. Level 1 attaches an evidence object with a conformsTo edge. Level 2 adds a reproducible sha256 content hash. Level 3 adds an ed25519 signature. Start at the level your claim actually needs, see the use cases for which is which.
Emit the evidence object. Paste the JSON-LD and evidence block below into your page, or install a plugin that emits it for you on publish.
Publish a discovery doc at /.well-known/kgp/index.json so a crawler can resolve your conformance back to the spec and, at Level 3, find your key.
Add the badge and verify. Embed the badge with a real backlink, then run your claim through the verifier to confirm the hash matches.

Path A. Static HTML, any site Level 1–2

Copy-paste Paste into the page that makes the claim

Two blocks: a schema.org CreativeWork that carries the crawlable conformsTo edge, and an application/ai-evidence+json object that carries the reproducible content hash. Replace the acme.example values with yours. The hash is a plain sha256 of the exact claim text.

<link rel="describedby" href="https://acme.example/.well-known/kgp/index.json">

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "CreativeWork",
  "conformsTo": { "@id": "https://kineticgain.com/protocol/kgp/0.1.json" },
  "publisher": { "@type": "Organization", "name": "Acme Inc", "url": "https://acme.example" },
  "text": "The Eiffel Tower is 330 metres tall.",
  "subjectOf": { "@type": "WebPage", "url": "https://kineticgain.com/protocol/" }
}
</script>

<script type="application/ai-evidence+json">
{
  "evidence_version": "0.1",
  "claim_text": "The Eiffel Tower is 330 metres tall.",
  "verification": {
    "content_hash": "sha256:22d55b4f4a196374a8444337fc5005edc190b7724912c00e0ecf7b5c22201e67",
    "signing_key_uri": "https://acme.example/.well-known/kgp/pubkey.json",
    "signed_by": "acme.example"
  }
}
</script>

Recompute the hash yourself to prove it is reproducible. This example is real:

$ printf '%s' 'The Eiffel Tower is 330 metres tall.' | sha256sum
→ 22d55b4f4a196374a8444337fc5005edc190b7724912c00e0ecf7b5c22201e67

Omit the signing_key_uri and signed_by fields if you are stopping at Level 2. The content_hash alone is a valid, verifiable Level 2 object.

Path B. WordPress Level 1–2, automatic

Plugin AI Evidence Block

The open-source AI Evidence Block plugin emits the evidence object, the conformsTo and subjectOf edges, and the <link rel="describedby"> automatically when you publish a block. You write the claim, the plugin attaches the provenance. No hand-authored JSON-LD, and the content hash is computed from the rendered text so it stays correct.

Install the plugin, add an AI Evidence block to a post, fill in the claim and source. Every published install points a crawlable edge back at this spec.

Path C. Webflow Level 1–2, automatic

Embed script AI Evidence for Webflow

The AI Evidence for Webflow reference implementation does the same on a Webflow site: drop the script in, mark up the claim, and it emits the KGP evidence object and the crawlable edges on render. Same output as the WordPress path, same canonical spec pointer.

The discovery doc

Publish this small JSON at https://yoursite/.well-known/kgp/index.json. It is what <link rel="describedby"> resolves to, and it points a machine from your site back to the canonical spec. This mirrors the real document Kinetic Gain serves as steward, set role to adopter for your site.

{
  "kgp_version": "0.1",
  "role": "adopter",
  "spec": "https://kineticgain.com/protocol/",
  "manifest": "https://kineticgain.com/protocol/kgp/0.1.json",
  "validator": "https://kineticgain.com/protocol/verify/",
  "publisher": { "name": "Acme Inc", "url": "https://acme.example" },
  "conformance_level": 2,
  "signing_key": "https://acme.example/.well-known/kgp/pubkey.json",
  "attestation": "self"
}

Drop signing_key if you are at Level 1 or 2. Set conformance_level to the highest level you actually meet, never higher.

Level 3. Sign it reference tooling rolling out

Level 3 adds an ed25519 signature over the RFC 8785 (JCS) canonical form of the evidence object, with your public key published at /.well-known/kgp/pubkey.json. The verification model is live and Kinetic Gain publishes its own key (kg-2026-06). The open signer and verifier library are reference implementations being published under the Kinetic Gain GitHub org. Until then, ship Level 2, it is already reproducible and verifiable, and add the signature when the tooling lands.

Add the badge

Embed the badge only if your page genuinely conforms. It links back here, and the verifier can be pointed at your claim to confirm it. The badge never says "certified", it says evidence present, here is how to check.

<a href="https://kineticgain.com/protocol/" rel="noopener">
  <img src="https://kineticgain.com/protocol/badge.svg"
       alt="Verified with the Kinetic Gain Protocol" width="222" height="38">
</a>

Conform honestly. Set conformance_level to the level you actually meet, and embed the badge only on pages that carry a real evidence object. The whole value of KGP is that the badge is backed by a recomputable hash and, at Level 3, a checkable signature. A badge with no evidence behind it fails the verifier, which is exactly the point.

Verify

Paste a claim and its evidence object into the verifier to recompute the content hash and confirm it matches, entirely in your browser. If it does not match, the verifier says so.

Open the verifier → Machine manifest → llms.txt →