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 provenance-tracked research agent that aggregates, cross-references, and synthesises data from verified sources. Every research output carries identity-anchored source attribution, making findings resolver-verifiable and commercially legible.
2Who It Is For
Research teams, analysts, and developers building automated research workflows. Ideal for organisations where research outputs must be traceable to verified sources for academic integrity, regulatory compliance, or commercial trust.
3Why ECZ-ID Matters Here
Research without provenance is opinion. ECZ-ID transforms research outputs into resolver-verifiable, identity-anchored intelligence where every finding can be traced back through verified source chains.
4Architecture
Multi-Source Aggregator
Collects data from multiple verified sources with identity-tracked provenance for each source.
Cross-Reference Analyser
Identifies patterns and correlations across sources while maintaining source identity chains.
Provenance Engine
Tracks the complete provenance chain from raw source to synthesised output.
Source Attribution Chain
Links every claim and finding back to its verified source identity.
Synthesis Compositor
Combines findings into structured research outputs with embedded trust metadata.
Verification Endpoint
Exposes verification endpoints for any consumer to validate research provenance.
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
- Dataset Passport
Recommended Passports
- API Passport
- AI Model 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 the research agent’s ECZ-ID through Resolver.
Trace research provenance
Follow any research finding back through its source chain via Resolver.
Verify source identity
Confirm the identity of data sources used in research outputs.
Validate synthesis chain
Verify the complete synthesis chain from sources to final output.
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 does not guarantee source data quality. Provenance verification is separate from content quality.
- Research synthesis quality depends on model capability and configuration.
- Source attribution is only as complete as the identity hooks configured.
- ECZ-ID provenance does not constitute peer review or academic validation.
Ready to Build This Agent?
Start with the build steps above, credential through TrustOps, and deploy your resolver-verifiable agent anywhere.