AmpliHive rides on your system.
The moment you install it, your LLM gets a signature.

Install the Drop-In

Pick the language you already use. The SDKs have identical shape: sign(), wrap(), verify(). No re-architecture. No proxy. No data path change.

Copy$ npm install @hivery/amplihive

Copyimport { AmpliHive } from "@hivery/amplihive";
import OpenAI from "openai";

const openai = new OpenAI({ apiKey: process.env.OPENAI_API_KEY });
const hive   = new AmpliHive({
  tenantDid: "did:hive:acme",
  apiKey: process.env.AMPLIHIVE_API_KEY,
});

// Your LLM stays on your side.
const llm = await openai.chat.completions.create({
  model: "gpt-4o-mini",
  messages: [{ role: "user", content: prompt }],
});
const text = llm.choices[0].message.content;

// AmpliHive signs the (prompt, response) pair.
const cert = await hive.sign({ prompt, response: text });
console.log(cert.certificate.alg);  // "ML-DSA-65"

Copy$ pip install amplihive

Copyfrom openai import OpenAI
from amplihive import AmpliHive

openai = OpenAI(api_key=os.environ["OPENAI_API_KEY"])
hive   = AmpliHive(
    tenant_did="did:hive:acme",
    api_key=os.environ["AMPLIHIVE_API_KEY"],
)

# Your LLM stays on your side.
llm = openai.chat.completions.create(
    model="gpt-4o-mini",
    messages=[{"role": "user", "content": prompt}],
)
text = llm.choices[0].message.content

# AmpliHive signs the (prompt, response) pair.
cert = hive.sign(prompt=prompt, response=text)
print(cert.certificate.alg)  # "ML-DSA-65"

Try it now

Five stages, one ML-DSA-65 certificate, in the same call: COMPILE → COMPRESS → AMPLIFY → CERTIFY → WRITEBACK. Pick a partner attribution and watch it bind into the signed payload. Tamper any byte and verify fails.

Why the widget can't be hacked once it's on the counter

The drop-in is a sealed transit layer. It carries proof, not power. If anything in transit is altered, the certificate breaks.

FAQ