# Introduction

### What is the KRNL Protocol?

KRNL is a plug-and-play protocol that extends enterprise systems with secure, cryptographically verifiable access to external APIs, AI systems, blockchain data, and traditional business applications. Every workflow step is executed off-chain in an isolated sandbox, cryptographically signed, timestamped, and delivered with a verifiable proof, enabling your systems to confirm authenticity before any state change, payment, or compliance action occurs.

### Why does it matter?

Enterprise systems face a critical gap: how do you prove that an off-chain event: an API call, a data transformation, or an AI-generated output, actually happened as claimed before it triggers a financial transaction, compliance action, or record update?\
\
Traditional middleware requires trust in centralized operators. Logs can be altered. APIs can fail silently. AI outputs cannot be audited retroactively. KRNL closes this gap by providing cryptographically verifiable proof of every external interaction, creating immutable audit trails that satisfy regulatory requirements and internal risk controls.\
\
When a system record triggers a payment, a document requires tamper-evident verification, or an AI model produces a decision, KRNL delivers the cryptographic evidence that proves the trigger was legitimate, the data was unaltered, and the execution occurred exactly as defined.

### What Can You Build?

As a flexible middleware layer, KRNL powers enterprise-grade use cases across compliance, security, and cross-system automation:\
\
**Secure Document Management** Upload, share, and view sensitive documents with cryptographically anchored fingerprints and identity-bound watermarking. Every viewer receives a personalized watermark tied to their identity, ensuring full accountability and leak traceability. Even if a document is screenshotted or exported, the watermark remains tied to the viewer.\
\
**CRM Workflow Automation** Connect customer relationship management systems to verifiable actions: loyalty programs triggered by deal stage changes, verifiable credential issuance on customer onboarding, or reputation scores updated from engagement data. Every trigger is cryptographically signed and auditable.\
\
**Pre-Transaction Compliance** Screen every action against regulatory, AML, and policy rules before execution. Validate sender provenance, sanctions exposure, and license constraints at the intent stage with verifiable, deterministic enforcement that auditors can independently verify.\
\
**Verifiable AI Decisioning** Run AI models off-chain for credit scoring, risk assessment, or fraud detection. KRNL signs the inference result and model version, delivering a proof that your compliance team can audit and your systems can trust before acting on the output.\
\
**Cross-System Orchestration** Bridge enterprise systems with settlement, identity verification, or asset tokenization—all through a single integration layer with end-to-end cryptographic proof.\
\
**Supply Chain & Provenance** Track goods, documents, or digital assets across multiple systems with tamper-evident verification at every handoff. Each step generates a cryptographic receipt that proves when, where, and by whom the transfer occurred.

### Getting Started

Choose your path based on your goals:

* **Platform Integrations** — Jump to [Enterprise Integrations](https://www.kimi.com/chat/19e1549c-9682-8edf-8000-0932619ab22b?chat_enter_method=history#) to explore pre-built connectors for popular enterprise platforms.
* **Custom Enterprise Workflow** — Open [KRNL Studio](https://studio.krnl.xyz/) to visually construct workflows connecting your existing APIs and systems without writing DSL by hand.

### Need Help? <a href="#need-help" id="need-help"></a>

If you feel stuck somewhere, or if you have any feedback or even if you want to say hello, you can reach out to Discord:

* Join the [KRNL Discord Server](https://discord.gg/krnl-labs).

### What's next?

{% content-ref url="/pages/5Wf7JaZ8RRXkzSWLMabk" %}
[Getting Started](/getting-started/getting-started-with-krnl.md)
{% endcontent-ref %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.krnl.xyz/getting-started/readme.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.