@verifiedstate/crewai

Your CrewAI Agents Trust Each Other. Should They?

VerifiedState integration for CrewAI. Adds cryptographic verification receipts to every assertion your CrewAI agent makes.

Install

npm install @verifiedstate/crewai

Quick Start

import { VerifiedStateCrewai } from '@verifiedstate/crewai';

const memory = new VerifiedStateCrewai({
  apiKey: 'vs_live_...',
  namespaceId: 'your-namespace-uuid',
});

// Store and verify a fact from your CrewAI agent
const { artifact, assertions, receipts } = await memory.storeAndVerify(
  'Customer prefers dark mode and uses PostgreSQL'
);

console.log(receipts[0].status);           // "verified"
console.log(receipts[0].final_confidence); // 0.94

// Query verified memory
const results = await memory.query('What database does the customer use?');
console.log(results.answerable);     // true
console.log(results.channels_used);  // ["sparse", "dense"]

Why

Every fact your CrewAI agent stores should come with proof — a signed receipt showing what the claim is, what evidence supports it, and whether it's been challenged or superseded.

Without verification receipts, you have the agent's output. You don't have the reasoning.

API

store(content, sourceId?)

Store content from your CrewAI agent.

extract(artifactId)

Extract structured assertions.

verify(assertionId)

Verify an assertion, produce a signed receipt.

storeAndVerify(content, sourceId?)

All-in-one: store, extract, verify.

query(queryText, limit?)

Six-channel retrieval with abstention.

health()

Namespace health metrics.

Links

• Documentation
• Integration Guide
• Get API Key

License

MIT