Dify Platform. Memory Plugin with Verification.

Verified memory for Dify AI applications.

Get API Key →

12MCP tools

0.01mslookup

Freefor individuals

ed25519signed

The Problem

Dify connects workflows. Facts flow between nodes unsigned. There's no verification of what was generated, no receipts, no audit trail through the pipeline.

Step 1

Connect

→

Step 2

Ingest + Extract

→

Step 3

Verify + Receipt

The Fix

npm install @verifiedstate/dify

Beta: tagging-level integration. Ingestion works via @verifiedstate/sdk with Dify-specific source tagging. Native Dify features coming.

textBeta
// Configure VerifiedState as a Dify tool provider
// Facts stored through Dify get verified automatically

What You Get Back

✓ VERIFIED

receipt.json
{
  "receipt_id": "rct_7f3a...",
  "assertion": "User prefers dark mode",
  "status": "verified",
  "confidence": 0.94,
  "signature": "ed25519:a8c3f1...",
  "verified_at": "2026-04-06T14:32:01Z",
  "chain_position": 42
}

Without VerifiedState vs. With VerifiedState

Feature	Without	With VerifiedState
Pipeline facts	Unverified	Signed receipts
Cross-workflow memory	None	Persistent verified store

FAQ

How does it integrate?

As a Dify tool provider plugin. Configure once, use in any workflow.

Related Integrations

Start building with verified memory.

Free: 50,000 assertions/month. No credit card. No trial expiration.

Get Free API Key Read the Docs GitHub →