Developer Onboarding
This site is your discovery and build gateway. TrustOps is where you acquire credentials. Resolver is where you prove identity. Here's how the complete journey works.
Three Surfaces, One Journey
ECZ-ID operates across three distinct surfaces. Understanding where each responsibility lives is the key to a smooth developer experience.
Developer Gateway
You Are Here
This is your discovery and build surface. Explore agent archetypes, browse starter kits, follow guided build flows, and understand the complete ECZ-ID domain map. This is where you start and where you return after credentialing.
- Discover agent patterns and starter kits
- Follow guided build flows
- Identify required trust objects
- Complete integration after credentialing
TrustOps
Credentialing Checkpoint
TrustOps is the provisioning authority. This is where you acquire your ECZ-ID passports, agent credentials, API keys, and production configurations. All credentialing, sales, and credential lifecycle management happens through TrustOps.
- Acquire ECZ-ID Business Passport
- Provision Agent Credentials
- Receive API keys and manifests
- Manage credential lifecycle
Resolver
Verification Surface
Resolver is the public verification surface. Any party can verify any ECZ-ID without needing an account. This is where identity claims are proven, trust scores are queried, and provenance chains are traced.
- Verify any ECZ-ID identity
- Query trust scores
- Trace provenance chains
- Public, no account required
Understanding the Complete Identity System
Before you build, understand what the system contains and how the pieces fit together.
ECZ-ID Business Passport™
The parent passport. Root credential for every organisation. All child passports, packages, and derived add-ons attach here.
7 Categories / 33 Child Passports
Digital & Operational, Product, Risk & Transfer, Robotics, Road & Freight Mobility, Aerial Mobility, Infrastructure-Grade, and Control & Trust Overlays.
25 Packages
17 core packages + 1 KYA Ready Pack™ + 7 advanced infrastructure services. These are the commercial acquisition objects shown in TrustOps for activating child passports and enterprise extensions.
ECZ-ID Insurability Readiness™
Derived add-on. NOT a package. Auto-computed from trust posture. Indicates readiness for insurer engagement.
Badges & Public Proof
After verification, entities receive resolver-verifiable badges—public proof URLs that anyone can check without an account.
Deployment
After credentialing and verification, deploy to any infrastructure. ECZ-ID identity travels with your entity. No vendor lock-in.
The Midpoint Credentialing Model
Why credentialing at the midpoint produces better agents than credential-after-build.
Why Not Build First, Credential Later?
Agents built without identity infrastructure require retrofitting. Identity hooks bolted onto finished agents are weaker, harder to maintain, and produce less trustworthy audit trails. The midpoint model ensures identity is woven into the architecture from the start.
Why Not Credential First, Build Later?
Developers need to understand what they're building before they can specify the correct trust objects. The initial build steps clarify the agent's architecture, boundaries, and capabilities—information needed for accurate credentialing.
The Midpoint Is the Sweet Spot
By the midpoint, you understand your agent's needs. You can specify exactly which passports and capabilities are required. The remaining build steps then integrate those real credentials into the agent's architecture, producing a genuinely verified, commercially legible agent.
The Complete Journey
What Comes Back from TrustOps
After credentialing in TrustOps, you return with concrete artefacts that integrate into your agent.
Agent ECZ-ID
A unique, resolver-verifiable identity string for each agent. This is the agent's permanent identity anchor.
Credential Manifest
JSON configuration containing capability attestations, operational boundaries, and delegation permissions.
Production API Keys
ECZ-ID API keys for identity context injection, verification hooks, and audit trail generation.
Trust Score Baseline
Initial trust score configuration. Scores are earned through operational history with real credentials.
How to Resume and Finish the Build
After acquiring credentials from TrustOps, you return to the Developer Gateway to complete integration.
Inject Your Credentials
Add Agent ECZ-ID, API keys, and credential manifest to your agent configuration. Each starter kit specifies exactly where these go.
Wire Identity Hooks
Connect ECZ-ID identity context injection to your agent's action pipeline. Every action gets verified identity context automatically.
Test in Sandbox
Run your complete agent in the ECZ-ID sandbox environment. Verify identity flows, check provenance chains, and validate audit trails.
Verify Through Resolver
Use Resolver to verify your agent's identity, check trust scores, and trace provenance chains end-to-end.
Deploy to Production
Deploy your resolver-verifiable agent to any infrastructure. ECZ-ID identity travels with your agent.
What You Need to Get Started
Prerequisites for the ECZ-ID developer experience.
SDK Capabilities
The ECZ-ID SDK handles identity complexity so you can focus on building.
Need Help?
Developer support is available through TrustOps. Architecture guidance, integration patterns, deployment planning, and custom configurations.
Contact via TrustOps ↗Ready to Start Your Journey?
Choose a starter kit to begin, or credential directly through TrustOps.