Dify Agents are increasingly running in production. They approve, pay, and send. But when a regulator, auditor, or counterparty later asks what an agent was authorized to do, internal logs may not be enough for independent verification.

Logs remain essential for understanding how a workflow ran. Signed receipts add another layer: evidence that can be verified outside the system that produced it.

This is the gap our ecosystem partner Asqav is built to close.

Asqav acts as an independent signing layer for agent actions. For each action routed through the plugin, it creates a receipt that binds the agent identity, the submitted action, and the authorization decision recorded at signing. The receipt is tamper-evident, so later changes to the signed record will cause verification to fail. Anyone with the receipt can verify it independently, without access to the originating Dify workspace or an Asqav API key. When placed before a sensitive step, Asqav can also act as a live authorization gate. An action that does not satisfy the configured policy can be stopped before the workflow proceeds.

What Asqav brings to Dify

A signed receipt for every action that counts: For each action routed through Asqav, the plugin connects the agent identity, action payload, and authorization result in a cryptographically signed receipt that a third party can verify.

Authorization decisions you can verify: Asqav creates signed records for both allowed and blocked actions, preserving the policy decision returned at signing.

A gate, not a rubber stamp: The same call that signs the record checks the action against configured policies. Dify can branch on the result so an out-of-bounds action is stopped before the downstream step runs.

Multi-party authorization for high-risk actions: The Request Action tool keeps an action pending until the required approvers have signed off, providing an additional checkpoint for sensitive steps.

Signatures built for long-term verification: Allowed actions are signed with ML-DSA-65, the post-quantum signature standard specified in NIST FIPS 204. Asqav also supports per-agent hash chains and timestamp anchoring to make later alteration or reordering detectable.

Evidence your audit program can lean on: Asqav receipts back the audit-trail requirements under the EU AI Act (Article 12), DORA (Article 17), SEC Rule 17a-4, HIPAA (Section 164.312(b)), and Regulation B, and roll up into ISO 42001 and SOC 2 evidence.

"Dify lets agents act. Asqav lets enterprises prove it. With regulated AI, the question is no longer whether the model worked, but whether its actions hold up under a formal challenge."

- Ali Ashkir, Co-founder, Asqav

Quick start

1. Install the Asqav plugin from Dify Marketplace

Search for Asqav in Dify Marketplace and install it. The plugin adds three nodes you can drop into any Dify workflow: Sign Action, Verify Signature, and Request Action.

The Asqav plugin on the Dify Marketplace.

2. Add your credentials

Drop in your Asqav API key and the agent identity that will sign. Dify verifies the plugin, Asqav signs what the agent does.

The Asqav credential panel, with API key and agent ID.

3. Place Sign Action after the LLM or Agent node

Place the Sign Action node right after the node that produces the decision (your LLM or Agent node), and before any irreversible action. The node takes an action_type plus optional context, signs the record, and returns an authorized flag along with a signature_id.

The Sign Action node placed after the LLM or Agent node, ahead of the If-Else gate.

4. Gate on the authorized result

Add an If-Else node that continues only when Asqav returns authorized with a signature_id, and route the false branch to a blocked end or human review.

The If-Else node checking the returned authorized result.

5. Verify on the allowed branch

Add Verify Signature on the allowed branch, which confirms the signature with no API key, then fire your real business action carrying the signature_id and verification_url with the record.

The Verify Signature node on the allowed branch, with the denied branch routed to a blocked end.

A loan decision you can defend six months later

A digital lending team runs personal-loan reviews on Dify. A borrower applies for $25,000. The LLM drafts an approve, deny, or refer recommendation. An Agent node calls credit, fraud, and AML/KYC services in parallel. Before anything irreversible happens, Asqav signs the decision payload, and the authorized result routes the workflow to each outcome with the receipt attached.

The flow at a glance: Knowledge retrieval → LLM or Agent decision → Credit, fraud, and AML/KYC checks → Asqav signs the decision payload → If-Else authorized gate → Approve, deny, or refer

Six months later, the borrower comes back. They challenge the decision. Did the policy version change between then and now? Was the model output edited after the fact? Were the reason codes reconstructed to fit the outcome?

Without Asqav, the team is left asking everyone to trust its logs.

With Dify and Asqav working together, the team produces a receipt that proves the exact payload existed, was signed by that agent's key, and was chained at the time of action. The audit team gets evidence, not assertions. The regulator gets verification, not narration.

That is the difference between logs and evidence. And it is what turns a working Dify Agent into a defensible one.

Get started today

Install the Asqav plugin from Dify Marketplace, or open the ready-made "Evidence Layer for AI Agent Actions" template directly in your workspace, and start turning your Dify Agent actions into verifiable receipts in minutes.

Asqav plugin ↗

Evidence Layer for AI Agent Actions ↗ (Template)

About Asqav

Asqav is the evidence layer for AI agents. It is an unaffiliated third party that signs each important agent action server-side, the moment it happens, and returns a tamper-evident receipt that anyone can verify with an open, neutral verifier. Because Asqav holds the keys and is not the agent’s operator, the recorded party cannot forge or backdate its own record.

Every action is signed with ML-DSA-65 (FIPS 204, post-quantum), chained per agent by SHA-256, and anchored in time with RFC 3161 and OpenTimestamps. Each receipt binds intent, the policy decision, execution, the hash chain, and the timestamp, so a reviewer can confirm what an agent set out to do, whether policy allowed it, and what actually ran.

Asqav ships Python and TypeScript SDKs, optional policies, guardrails, and multi-party approvals, and produces audit packs in regulator-ready shapes for the EU AI Act, DORA, NYDFS 500, HIPAA, SEC 17a-4, and more. The Compliance Receipts profile is a public IETF Internet-Draft (draft-marques-asqav-compliance-receipts), so what ships is what the standard says.

Asqav gives teams cryptographic proof of every agent action, in a shape regulators can read on first pass.

⁠Website | ⁠GitHub | Docs | ⁠X | LinkedIn

About Dify

Dify is an open-source, production-ready platform for building agentic AI applications. It gives enterprises and developers an intuitive low-code interface to build, deploy, and operate generative AI applications at speed.

As of July 2026, Dify has surpassed 153+ GitHub stars, making it one of the most widely adopted open-source AI projects in the ecosystem.

Built around core capabilities including workflow orchestration, agent frameworks, data management, and model integration, Dify significantly lowers the barrier to adopting advanced AI technologies. Wwhether you are an independent developer or part of a large organization. Teams ship AI-powered workflows faster, with less engineering overhead and lower operational cost, turning generative AI from an experiment into a sustainable business advantage across operational automation, knowledge services, customer support, and intelligent analytics.

Website | GitHub | Docs | X | LinkedIn | Discord | YouTube