Live · receipts.thehiveryiq.com/v1/verify Patent Pending

XCALIBUR VERIFY

This gives you a zero-knowledge proof that every piece of context fed into your AI prompt really belongs to your corpus. You can check it yourself. So can your regulator. You don't have to take our word for it. You can check the math.

ML-DSA-65 · FIPS 204 Merkle corpus commitment Tenant-isolated Live demo below Patent Pending
Here's the question: "Did that context actually come from my corpus?" Here's the answer: a proof you can check yourself, without trusting anyone.
Live pipeline

VERIFY rides on top of CCACW

This is the fourth piece of XCALIBUR. It runs after AMPLIFY and before the response leaves the rail. Every corpus entry that gets injected earns a Merkle inclusion proof, and the whole certificate gets signed with a post-quantum key.

CALLER
COMPILE
COMPRESS
LLM
AMPLIFY
VERIFY
CALLER + cert
Corpus Merkle tree · proof path highlighted
ROOT · SIGNED H(A·B) H(C·D) ENTRY A ENTRY B ENTRY C ENTRY D proof path · Entry A injected
Verify certificate · live values populate on run
version"xcalibur-verify/v1"
commitment_rootclick Run Verification →
commitment_vernot run yet
proof_mode"standard"
leaf_hashnot run yet
siblings[]not run yet
original_hashnot run yet
injected_hashnot run yet
fidelity_scorenot run yet
signaturenot run yet
validnot run yet
Calls POST /v1/verify/demo/run on receipts.thehiveryiq.com · real Merkle, real signature
What VERIFY proves

Three claims, one certificate

01 · Corpus membership

The injected context is yours

The context that gets injected into your prompt is a verified member of your committed corpus. It's not made up, and it's not swapped in from somewhere else. It's provably yours.

02 · Zero contamination

No tenant can spoof your proof

We build a hard cryptographic wall between tenants right when we generate the proof. No other tenant's corpus can ever produce a valid proof against your commitment root.

03 · Content intact

Nothing slipped in or out

We hash your original prompt content and bind it into the certificate. The SHA3-256 commitment proves nobody inserted, swapped, or changed anything before it reached the LLM.

Why nobody else has this

Logging is not a proof

Azure OpenAI · AWS Bedrock · Vertex

Their attestation is really just a logging system. You have to trust their audit trail, and you can't independently check corpus membership yourself. Your regulator audits them. You still never get to check the math.

No proof · trust required

LlamaIndex · LangChain · AutoGen

RAG frameworks inject context with nothing backing it up. Whatever the prompt got is just whatever the framework happened to retrieve. No commitment, no proof, no receipt.

No attestation

EAS · Sismo · Galxe Passport

These tools attest to identity claims on-chain. That's a different problem. They don't touch inference context, corpus membership, or AI prompt integrity at all.

Wrong layer

XCALIBUR VERIFY

Your corpus gets Merkle-committed and the root gets signed with ML-DSA-65. Every call gets its own inclusion proof, and you can check it yourself at a public endpoint. No trust required, and it's hardened against quantum attacks. Patent Pending.

Only this exists
Public API · live now

Five endpoints, one base

All paths live under https://receipts.thehiveryiq.com. The proof verification endpoint needs no login, so auditors can hit it directly.

GET/v1/verify/statusService health, signature algorithm, demo corpus size
POST/v1/verify/commitment/buildBuild a signed Merkle commitment for a tenant's current corpus
GET/v1/verify/commitment/{tenant_id}/currentPublic lookup of a tenant's current signed commitment
POST/v1/verify/proof/generateInclusion proof for an entry, in standard or zk mode
POST/v1/verify/proof/verifyVerify proof + commitment without trusting the server
POST/v1/verify/disputeCaller dispute with 24h resolution against retained corpus snapshot
POST/v1/verify/demo/runEnd-to-end pipeline run, the same call this page's button makes
LIVE · receipts.thehiveryiq.com/v1/verify XCALIBUR umbrella → AmpliHive widget → Pricing → Patent Pending