Build Your Own ECZ-ID-Backed Agent
A master guided flow for building custom agents with verified identity. Choose your archetype, choose your stack, credential through TrustOps at the midpoint, then complete, verify, and deploy anywhere.
1Choose Your Archetype
What kind of agent are you building? Your archetype determines the required trust objects and recommended integration patterns.
Skill Agent
Single-purpose agent executing defined skills (extraction, classification, summarisation).
Orchestrator / Subagent
Primary agent delegating to specialised subagents with credential propagation.
API Workflow Agent
Multi-step API orchestrator with identity-verified handoffs at every boundary.
Compliance / Evidence Agent
Evidence collector and audit assembler with provenance-anchored outputs.
Operations / Incident Agent
Monitoring, anomaly detection, and incident response with verified chains.
Research / Intelligence Agent
Source aggregation, cross-referencing, and provenance-tracked synthesis.
Support / Intake Agent
Request handling, triage, routing, and SLA tracking with identity context.
Platform Integration Agent
Bridge into existing platforms (OpenClaw, Claw) with ECZ-ID trust anchoring.
Custom Agent
Build anything from scratch with the Generic Python Starter and ECZ-ID hooks.
2Choose Your Stack
ECZ-ID is stack-agnostic. Choose the technical foundation that fits your team and use case.
Anthropic Claude
Claude-powered agents with native Claude API integration. Best for teams already invested in the Anthropic ecosystem.
MCP (Model Context Protocol)
Model-agnostic agents that can switch between LLM providers. Best for avoiding vendor lock-in.
Python Native
Pure Python agents with no LLM dependency. Best for deterministic workflows and custom processing.
Platform Bridge
Integration with existing agent platforms (OpenClaw, Abacus Claw). Best for extending existing deployments.
3Identify Required TrustOps Package
Based on your archetype and stack, identify which ECZ-ID passports and packages you need to acquire.
| Archetype | Minimum Required | Recommended Additional | Package |
|---|---|---|---|
| Skill Agent | Business Passport + Agent Credential | API Passport, Software Supply Chain | Agent Starter Package |
| Orchestrator / Subagent | Business Passport + Agent Credentials (each) | AI Model Passport | Agent Starter Package |
| API Workflow | Business Passport + Agent Credential + API Passport | Cyber Resilience Passport | API Trust Package |
| Compliance Agent | Business Passport + Agent Credential + Risk & Policy | Dataset Passport, Cyber Resilience | Compliance & Governance Package |
| Operations Agent | Business Passport + Agent Credential | Cyber Resilience, IoT Device Passport | Operations Package |
| Research Agent | Business Passport + Agent Credential + Dataset Passport | API Passport, AI Model Passport | Data & Research Package |
| Support Agent | Business Passport + Agent Credential | API Passport | Agent Starter Package |
| Platform Bridge | Business Passport + Agent Credential + API Passport | Software Supply Chain, AI Model | Platform Integration Package |
4TrustOps Credentialing Checkpoint
TrustOps Credentialing Checkpoint
Pause here to acquire your required ECZ-ID trust objects
This is a designed pause point in your build process. Before continuing, you need to acquire the required ECZ-ID passports and credentials from TrustOps. This midpoint credentialing approach ensures your agent is built with verified identity from the start—not bolted on after the fact.
Required Passports
- ECZ-ID Business Passport
- Agent Credential
Recommended Passports
- API Passport
- AI Model Passport
- Dataset Passport
- Cyber Resilience Passport
- Risk & Policy Passport
- Software Supply Chain Passport
Relevant Packages
What You Must Acquire in TrustOps
What You Bring Back from TrustOps
5Acquire in TrustOps
TrustOps is the provisioning authority. All ECZ-ID passports, credentials, and API keys are acquired through TrustOps.
Why Midpoint Credentialing?
Credentialing at the midpoint means your agent is built around verified identity from the start. Retrofitting credentials onto a finished agent is harder, less secure, and produces weaker trust posture.
What Happens in TrustOps
You register your organisation, define your agent's capabilities and boundaries, select the required passport family and package, and receive your production credentials and API keys.
What You Bring Back
Agent ECZ-ID(s), credential manifests, production API keys, and trust score configuration. These are injected into your agent configuration in the next step.
6Return and Integrate
With your TrustOps credentials in hand, complete the final integration steps.
7Verify with Resolver
Resolver is the public verification surface. Any party can verify your agent's identity without needing an account.
Identity Verification
Query your agent's ECZ-ID through Resolver to confirm verified status, capability attestations, and trust score.
Output Provenance
Trace any agent output back through its provenance chain to the verified identity that produced it.
External Verification
Share your agent's ECZ-ID with partners, regulators, or customers so they can independently verify.
Trust Score Review
Monitor your agent's trust score and the factors contributing to it over time.
8Deploy Anywhere
ECZ-ID-backed agents are portable. Your verified identity travels with your agent regardless of deployment target. No vendor lock-in.
Ready to Start Building?
Choose a starter kit for a guided experience, or begin your custom build and credential through TrustOps.