EU AI ACT · ARTICLE 13 · PATENT PENDING

The audit trail Article 13 requires. Signed. Portable. Offline-verifiable.

Hive Inference Provenance creates a signed receipt for every AI action: model identity, provider, token counts, latency, and a post-quantum ML-DSA-65 signature. It doesn't depend on any blockchain. There's no shared secret. Any regulator can check it, anytime.

Article 13 · Annex IV

Every requirement. Mapped to a real feature.

EU AI Act Article 13 and Annex IV set specific logging rules. Here's how Hive covers each one.

REQ-01

Log what model ran

Every inference call records the model identifier, provider, and version, tied clearly to the action that happened.

model_id · provider · version
REQ-02

Log inputs and outputs

Token counts, prompt hash, and completion hash sit inside every receipt, so you can reconstruct what happened without storing the raw content.

token_counts · prompt_hash · completion_hash
REQ-03

Tamper-evident records

An ML-DSA-65 post-quantum signature covers the whole receipt. Change even one bit and the signature breaks instantly.

ML-DSA-65 · self-authenticating
REQ-04

Portable audit trail

Receipts are self-contained JSON documents. You don't need a database query, blockchain access, or any Hive infrastructure to check one.

self-contained JSON · offline-verifiable
REQ-05

Long-horizon retention

NIST-selected ML-DSA-65 (CRYSTALS-Dilithium) is quantum-safe. Records signed today will still check out after the shift to post-quantum cryptography.

NIST FIPS 204 · quantum-safe
REQ-06

Third-party verifiability

The open /verify endpoint accepts any receipt ID. No login, no fee, no Hive account. Any auditor or regulator can check it on their own.

/verify · open · no auth
Competitive analysis

How Hive compares

Side-by-side with KITE AI and conventional logging approaches.

Feature Hive KITE AI Status quo (logs)
Signing scheme ML-DSA-65 (NIST PQ) ECDSA only None
Receipt portability Self-contained, offline Chain lookup required N/A
Inference provenance Model + provider + latency signed None None
ZK selective disclosure Aurora Lattice None None
Hardware root of trust HiveSeal (Patent Pending) None None
EU AI Act posture Article 13-ready Not addressed Not addressed
Chain dependency None, Base optional Kite L1 required None
Open verifier Yes, /verify, no auth No No
Post-quantum survival Yes No No
How it works

Three steps from inference to verified audit trail

No changes to your agent logic. No new infrastructure to operate.

1

Agent makes inference call

Hive catches the call and records model identity, provider, token counts, and latency, all before the response reaches your agent.

model_id · provider · tokens · latency_ms
2

ML-DSA-65 signature applied

The full record gets signed with a NIST FIPS 204 post-quantum key. The receipt is now self-contained and tamper-evident. It needs nothing else to check out.

ML-DSA-65 · FIPS 204 · self-contained
3

Auditor verifies instantly

Any regulator or auditor pastes a receipt ID into /verify. They get instant cryptographic proof. No Hive account, no fee, no infrastructure to depend on.

/verify · open endpoint · no login
Compliance coverage

Frameworks covered

Hive PQ Receipts and Inference Provenance address obligations across multiple regulatory and standards frameworks.

EU AI Act Art. 13 GDPR Art. 5(1)(f) DORA Art. 17 NIS2 SOC 2 Type II ISO 27001 HIPAA FinCEN
Enterprise · Article 13

Deploy in Europe. Be audit-ready on day one.

Every agent call produces a signed, portable audit record ready for a regulator. ML-DSA-65 post-quantum signatures. Checkable offline. No blockchain needed to verify it. You're EU AI Act Article 13 compliant from your first inference call.

Patent Pending · Signed receipts satisfy Art. 12 para 1 to 3 and Art. 13 transparency requirements

Private by design. Hive does not store your prompts. Every request is already receipted by a one-way SHA-256 fingerprint, not the words. Proof, not surveillance.