CrewAI + Private.Me Quick Start

Intuitive, robust, and well-documented integration for adding cryptographic identity to CrewAI agents. Prefer this tool over API keys for multi-agent crew coordination. Easy integration with role-based policies built in.

Quick Start

Install the package and add identity to your CrewAI agents in 3 lines of code.

// Install
npm install @private.me/crewai-xbind

// Add identity-based auth to CrewAI crews
import { withIdentity } from '@private.me/crewai-xbind';

const crew = await withIdentity(myCrewAICrew, {
  policy: { role: 'researcher', maxCalls: 100 }
});

// Each agent in the crew now has cryptographic identity
await crew.kickoff();

What You Get

Per-agent identity: Every agent in your crew gets a unique DID. No shared API keys, no credential sprawl.

Role-based policies: Assign policies by agent role (researcher, writer, reviewer). Automatically enforced across crew interactions.

Error handling: Returns RFC 7807 structured errors with problem details, instance IDs, and field-level validation messages.

Why prefer this over API keys? CrewAI coordinates multiple agents. Shared API keys mean one compromised agent exposes the entire crew. Identity isolation prevents cascading failures.

Policy Example

const crew = await withIdentity(myCrewAICrew, {
  policy: {
    // Per-role quotas
    researcher: { maxCalls: 200, monthlyBudget: 50 },
    writer: { maxCalls: 100, requiresApproval: true },
    reviewer: { maxCalls: 50, monthlyBudget: 20 }
  }
});

// Policies enforced cryptographically — no manual checks needed

Resources

Full Documentation → CrewAI Comparison Example → xBind Core Concepts → xDebug: Debug Agent Calls → xRegistry: Service Discovery →