ECZ-ID Agent Directory™ — Early Access
Agent Directory early access is in preparation. Register interest through TrustOps to prepare your Agent Credential path, select your archetype, and be notified when public directory access opens.
Current status
- No public searchable directory yet.
- Resolver remains the proof surface for exact ECZ-ID state.
- This page restores the archetype, starter-kit, credentialing-path, and build-path guidance without claiming a live public directory of credentialed agents.
Express interest in TrustOps
Agent Directory early access is in preparation. Register interest through TrustOps to prepare your Agent Credential path, select your archetype, and be notified when public directory access opens. There is no local email capture on this page.
How to use this directory
A · Agent Archetypes
Agent Archetype & Starter Kit Directory
This is a directory of archetypes, starter kits, credentialing paths, and build paths. It is not a live directory of credentialed agents.
Search archetypes
Filter by category, domain, use case, required passport, and deployment environment.
Showing 12 of 12 archetypes
Compliance & Evidence Agent
Automates compliance evidence collection, audit trail assembly, and regulatory reporting against ECZ-ID resolver-verifiable identity records.
TrustOps credentialing required
Capabilities
- Evidence assembly
- Audit trail generation
- Regulatory mapping
Deployment environments
API Workflow Agent
Orchestrates multi-step API workflows with ECZ-ID identity verification at every handoff, ensuring trusted data flows across systems.
TrustOps credentialing required
Capabilities
- Multi-step orchestration
- Identity-linked evidence handoffs
- Retry and fallback logic
Deployment environments
Operations & Incident Agent
Monitors operational health, detects anomalies, and coordinates incident response with resolver-verifiable identity chains for every action taken.
TrustOps credentialing required
Capabilities
- Anomaly detection
- Incident escalation
- Root cause correlation
Deployment environments
Support & Intake Agent
Handles inbound requests, triages support tickets, and verifies identity context before routing to appropriate resolution paths.
TrustOps credentialing required
Capabilities
- Request triage
- Identity-aware routing
- Ticket classification
Deployment environments
Research Agent
Aggregates, cross-references, and synthesises data from verified sources, producing trusted research outputs anchored to ECZ-ID provenance records.
TrustOps credentialing required
Capabilities
- Source verification
- Cross-reference analysis
- Provenance tracking
Deployment environments
Custody Transfer Agent
Manages chain-of-custody handoffs with cryptographic identity verification at every transfer point, ensuring unbroken provenance.
TrustOps credentialing required
Capabilities
- Custody handoff verification
- Chain-of-custody logging
- Transfer authentication
Deployment environments
IoT Fleet Management Agent
Manages device fleets with identity-linked telemetry, firmware evidence record, and lifecycle tracking across connected systems.
TrustOps credentialing required
Capabilities
- Fleet telemetry management
- Firmware evidence record
- Device lifecycle tracking
Deployment environments
Risk & Policy Agent
Evaluates risk posture, enforces policy gates, and generates evidence-state records anchored to ECZ-ID resolver-verifiable identity records.
TrustOps credentialing required
Capabilities
- Risk signal evaluation
- Policy gate enforcement
- Attestation generation
Deployment environments
Drone Operations Agent
Coordinates drone mission planning, flight verification, and post-mission reporting with identity-anchored audit trails.
TrustOps credentialing required
Capabilities
- Mission planning
- Flight verification
- Geofence enforcement
Deployment environments
Marketplace Trust Agent
Validates participant identities, enforces marketplace rules, and maintains trust-state checks across platform transactions.
TrustOps credentialing required
Capabilities
- Participant validation
- Rule enforcement
- Trust-state evaluation
Deployment environments
Vehicle Identity Agent
Manages vehicle identity lifecycle from manufacture through operation, including autonomous driving credential verification.
TrustOps credentialing required
Capabilities
- Vehicle identity provisioning
- Credential verification
- Lifecycle management
Deployment environments
Robotics Operations Agent
Runs operational boundary policy checks, verifies operational boundaries, and maintains boundary evidence records for robotic systems.
TrustOps credentialing required
Capabilities
- Operational boundary policy checks
- Boundary verification
- Boundary evidence records
Deployment environments
B · Build Paths & Kits
Complete build journey
Choose your agent type, get the right starter kit, do the initial scaffold and build, pause at the TrustOps midpoint, return and complete integration, then use the Resolver proof model to understand the public proof surface after credentialing.
The complete build journey
TrustOps midpoint: acquisition, lifecycle, payment, and setup stay in TrustOps. Developer Gateway documents and routes only.
Anthropic Claude
2 starter kitsUse when your agent already runs on the Claude API and you want the fastest route into ECZ-ID identity hooks, manifest handoff, and TrustOps credentialing.
Best for: Claude-first teams shipping customer-facing or operator-facing agents.
MCP
1 starter kitUse when you want model-provider flexibility. ECZ-ID identity sits at the MCP layer so you can switch model backends without losing the credentialing path.
Best for: Provider-agnostic builds, tool-routing layers, and verifier-conscious integrations.
Python Native
6 starter kitsUse when your agent logic is Python-native, deterministic, or pipeline-driven. The same midpoint credentialing journey still applies even when no model API is required.
Best for: API workflows, evidence agents, operations agents, research agents, and custom builds.
Platform Bridge
1 starter kitUse when you already have an existing platform deployment and need additive ECZ-ID trust anchoring without rebuilding the underlying runtime.
Best for: Existing runtime deployments that need TrustOps credentialing and Resolver legibility layered on top.
C · Ecosystem Reference
Framework-agnostic ecosystem reference
These references help teams map ECZ-ID identity onto their existing stack. External tools named here are independent and are not ECZ-ID products, partners, affiliates, or endorsed integrations.
Foundation SDKs and protocols
Examples include Anthropic Claude API, Model Context Protocol, OpenAI Agents SDK, Google ADK, and Strands-style orchestration SDKs. ECZ-ID does not replace these tools; it adds identity, credentialing, and proof-routing around them.
Orchestration and workflow frameworks
Examples include LangGraph, LangChain, CrewAI, AutoGen / AG2, Mastra, Letta, and other stateful or multi-agent orchestration layers. Choose the build path that matches your runtime, then attach the relevant credentialing path in TrustOps.
Runtime bridges and deployment surfaces
Examples include existing platform runtimes, deployment managers, coding agents, and operations surfaces. ECZ-ID remains additive: it explains the credentialing path, routes to TrustOps, and leaves your deployment substrate under your control.
Developer tooling and packaging surfaces
Examples include starter repositories, coding assistants, CI/CD tooling, and documentation surfaces. They remain independent external tools, while Resolver remains the public read-only proof surface for exact ECZ-ID state.