Multi-Agent

Your Crew Shares Memory. Now It Shares Proof.

Multi-agent workflows need shared memory. VerifiedState makes that memory trustworthy.

The Problem

CrewAI crews share context through tasks and tools. But there's no built-in persistent memory, no conflict detection when agents disagree, and no receipt when Agent A stores a fact that Agent B relies on.

Three agents. Conflict detected. Higher confidence wins.

• • • Research Agent

Q3 revenue: $4.2M (preliminary)

✓ Stored · rct_71ab · 0.82

• • • Fact-Check Agent

Q3 revenue: $4.7M (audited)

⚠ CONFLICT with rct_71ab

✓ Stored · rct_93cd · 0.96

• • • Writing Agent

> What's Q3 revenue?

⚠ Conflict detected — 2 values

$4.2M (preliminary, 0.82)

$4.7M (audited, 0.96) ← higher

Using $4.7M · rct_93cd

Conflicts surfaced. Confidence compared. Truth selected.

The Fix

npm install @verifiedstate/crewai

typescript
import { VerifiedCrewMemory } from '@verifiedstate/crewai';

const memory = new VerifiedCrewMemory({
  apiKey: 'vs_live_...',
  namespaceId: 'crew_research',
});

await memory.save('user_budget', 'Budget is $50,000 for Q3');
const results = await memory.search('Q3 budget');
// results[0].receipt.status → "verified"

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
Shared memory	Task context only	Persistent verified store
Agent disagreement	Last write wins	Conflict detection
Trust between agents	Implicit	Receipt-verified

FAQ

Does it work with CrewAI memory?

It replaces or augments CrewAI's built-in memory. Use it alongside task-level context for full coverage.

Start building with verified memory.

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

Get Free API Key Read the Docs GitHub →