Cloudflare+AmpliHive Co-brand wired Patent Pending

Verified Inference on the edge.
Every AI Gateway response signed under tenant DID, attributed to Cloudflare in the cert.

AmpliHive is the customer-side trust layer for AI Gateway, Workers AI, and any model traffic passing through Cloudflare. Each response is stamped with an ML-DSA-65 certificate binding prompt_hash, response_sha256, tenant_did, and partner_id=cloudflare — unforgeable attribution. You ship the “provable AI” checkbox enterprise CIOs already ask for. We take $0.06 per 1M signed calls. You take a negotiated cut. The ledger is the signed payload — no reconciliation theater.

Try the co-branded widget Install snippet Why AmpliHive
The wedge

What Cloudflare gets the day this ships

AI Gateway becomes auditable

Today AI Gateway gives caching, rate-limiting, and analytics. AmpliHive adds the missing layer: cryptographic provenance under FIPS 204 (ML-DSA-65). The same gateway, now defensible in a banking, healthcare, or gov procurement.

Workers AI gets a compliance moat

Bind every Workers AI response to a signed cert with partner_id=cloudflare inside the payload. Competitors can’t copy this in a quarter — PQ signing infra plus tenant DID plus corpus writeback is a year of work.

Zero-trust, edge-native, no data exfil

AmpliHive does not see the customer’s prompt body unless they opt in. We see hashes. The cert is signed against hashes. Drop it next to AI Gateway on the customer’s account — the customer’s data path stays at the edge.

Why this lands on the AI Gateway roadmap, not in conflict with it

Cloudflare’s edge wins on TTFT and reach. We don’t sit in that path. AmpliHive is a sidecar: the customer’s app calls AI Gateway, then calls hive.sign({prompt, response}). Total round-trip overhead is ~6ms p95 plus ~60ms ML-DSA-65 sign, off your critical path. AI Gateway’s latency story stays clean. Cloudflare’s compliance story becomes the best in the AI infra market.

  • Co-brand the AI Gateway dashboard with a “Cloudflare Verified Inference” PQ seal.
  • Ship as a Worker binding, an npm package, or a pip package — whichever surface area Cloudflare wants.
  • Every signed call carries partner_id=cloudflare. Revenue share is provable, not promised.
  • Sell into Cloudflare One Enterprise, Magic WAN compliance buyers, and federal accounts that close the tab on un-attested AI today.
Install snippet · co-branded

One line. Partner-attributed by default.

Customer keeps their Cloudflare AI Gateway URL. Customer keeps their data path. AmpliHive returns a cert. The cert says “signed for tenant X, attributed to Cloudflare.”

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

// Cloudflare AI Gateway in front of any provider
const ai = new OpenAI({
  apiKey: process.env.OPENAI_API_KEY,
  baseURL: "https://gateway.ai.cloudflare.com/v1/<account>/<gateway>/openai",
});

const hive = new AmpliHive({
  tenantDid: "did:hive:acme",
  apiKey: process.env.AMPLIHIVE_API_KEY,
  partnerId: "cloudflare",  // bound into the signed cert
});

const llm  = await ai.chat.completions.create({
  model: "gpt-4o-mini",
  messages: [{ role: "user", content: prompt }],
});
const text = llm.choices[0].message.content;

const cert = await hive.sign({ prompt, response: text });
console.log(cert.certificate.payload.partner_id); // "cloudflare"
console.log(cert.certificate.alg);                // "ML-DSA-65"
Live · partner_id pre-wired

Try it — signed under partner_id=cloudflare

Sign a real (prompt, response) pair against production. The cert payload will carry partner_id: "cloudflare". Try the “Tamper partner_id” button — the signature breaks. That’s the unforgeable attribution.

Result
Status: idle. Click “Sign with AmpliHive” to start.

Cloudflare revenue share — live calculator

Negotiable. Default 30%. Every signed call carries partner_id=cloudflare — share is provable, not promised.
$0.06 / 1M
30%
$1800.00
At 1B signed calls/month, that’s $18,000 / mo at 30% — on AI Gateway traffic Cloudflare already routes. The compliance unlock is the leverage. Move the slider.