Fast Start
What you will have in minutes
A locally running, ECZ-ID-backed agent scaffold with resolver-verifiable identity hooks, a credential manifest, and Resolver verification ready to run.
What you do first — in order
What comes back from TrustOps
- Agent ECZ-ID(s)
- Credential manifest (JSON, discovery only)
- API keys issued in TrustOps
Success looks like
Resolver returns a resolver-verifiable state for your Agent ECZ-ID. You can share it with any party without an account.
1What This Kit Builds
A minimal, unopinionated Python agent scaffold with ECZ-ID identity hooks pre-wired. This is the foundation template for building any custom agent type with resolver-verifiable identity from the ground up. No framework opinions, no platform lock-in.
2Who It Is For
Developers who want maximum flexibility in building custom ECZ-ID-backed agents. Ideal for teams with specific architectural requirements, uncommon agent patterns, or those building entirely new agent types.
3Why ECZ-ID Matters Here
Custom agents built without identity infrastructure become harder to credential retroactively. Starting with ECZ-ID hooks from the ground up means identity is woven into your architecture, not bolted on later. This produces agents designed for serious deployment.
4Architecture
Minimal Agent Core
A clean, extensible agent scaffold with no framework opinions, just the essential patterns.
ECZ-ID Hook Points
Pre-configured integration points for identity context injection, verification, and audit logging.
Configuration System
Environment-based configuration supporting development, sandbox, and production credentials.
Extension Framework
Clear extension points for adding custom capabilities while maintaining identity context.
Pattern Library
Example patterns for common integration scenarios: API calls, data processing, delegation.
Test Harness
Pre-built test fixtures for verifying identity flows in your custom agent logic.
5Build Steps Overview
Trust Map
Required Passports
Recommended Passports
Relevant Packages
What Each Enables
6TrustOps 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 resolver-verifiable identity from the start—not bolted on after the fact.
Required Passports
- ECZ-ID Business Passport
- Agent Credential
Recommended Passports
- API Passport
Relevant Packages
What You Must Acquire in TrustOps
What You Bring Back from TrustOps
9Return and Complete Integration
With your TrustOps credentials in hand, return here to complete the final build steps.
10Verify Through Resolver
Verify agent identity
Query your custom agent’s ECZ-ID through Resolver.
Verify custom outputs
Trace any output from your custom agent back to resolver-verifiable identity.
Test external verification
Have an external party verify your agent’s identity through Resolver.
Validate resolver state
Review your agent’s resolver state and contributing evidence factors.
11Deploy Into Your Environment
ECZ-ID-backed agents are portable. Your resolver-verifiable identity travels with your agent regardless of deployment target after TrustOps and Resolver checks. No vendor lock-in.
12Limits & Non-Claims
- This kit does not provision credentials. All credentialing happens through TrustOps.
- This kit provides scaffolding, not a complete agent. You build the custom logic.
- The generic template is unopinionated and requires architectural decisions from the developer.
- Identity hooks must be maintained as you build custom logic around them.
- Resolver state is built up through operational history with real credentials.
Ready to Build This Agent?
Start with the build steps above, credential through TrustOps, and deploy your resolver-verifiable agent anywhere.