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 focused skill agent powered by Anthropic Claude that carries verified ECZ-ID credentials. This kit produces an agent capable of executing defined skills—data extraction, document analysis, classification, summarisation—where every output is identity-anchored and provenance-tracked. The resulting agent is commercially legible and resolver-verifiable.
2Who It Is For
Developers and teams building Claude-powered skill agents for enterprise workflows, compliance automation, or customer-facing AI features. Ideal for organisations that need their AI outputs to be traceable to a resolver-verifiable identity for audit, regulatory, or commercial trust purposes.
3Why ECZ-ID Matters Here
Without resolver-verifiable identity, a Claude skill agent is an anonymous function. With ECZ-ID, every output carries provenance, every action is auditable, and every downstream system can verify who produced what. This transforms a useful tool into a commercially legible, insurer-legible, resolver-verifiable agent designed for serious deployment.
4Architecture
Claude API Layer
Direct integration with Anthropic Claude API for natural language processing, reasoning, and structured output generation.
ECZ-ID Identity Layer
Agent passport and credential management. Every API call and output is signed with resolver-verifiable identity context.
Trust Context Engine
Injects resolver-verifiable identity metadata into every agent action, enabling downstream verification through Resolver.
Structured Output Formatter
Formats agent outputs with embedded trust metadata, provenance chains, and verification endpoints.
Audit Trail Logger
Immutable, identity-anchored logging of every action, decision, and output for compliance readiness.
Skill Composition Framework
Composable skill patterns that maintain identity context across skill chains and handoffs.
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
- Software Supply Chain 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
Query your agent’s identity
Use Resolver to look up your agent’s ECZ-ID and confirm its resolver-verifiable state, capability evidence records, and current resolver state.
Verify an output
Take any agent output and verify its provenance chain through Resolver.
Check delegation chains
If using subagent delegation, verify the complete delegation chain through Resolver.
Validate resolver state
Query your agent’s current resolver state and review the evidence factors contributing to it.
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 ECZ-ID credentials. Credentialing happens through TrustOps.
- This kit does not guarantee Claude API availability. Anthropic API access is a separate dependency.
- This kit does not simulate verification. All verification happens through Resolver with real credentials.
- This kit does not replace compliance frameworks. It provides identity infrastructure that supports compliance.
- Resolver state is built up through operational history, not granted at provisioning.
Ready to Build This Agent?
Start with the build steps above, credential through TrustOps, and deploy your resolver-verifiable agent anywhere.