Agent Starter Kits
10 guided scaffolds, each with a built-in TrustOps credentialing checkpoint. Pick your kit, build initial setup, pause to acquire credentials, return, verify, and deploy. Every kit is framework-specific but all converge on the same TrustOps / Resolver journey.
Use this page as a selection map — compare archetypes, build paths, and trust routes. Each kit shows who it’s best for, what it builds, what passports are required, and what you can verify through Resolver once credentialed. Bookmark this page and return after TrustOps to complete your build.
Before you start
- Know which agent archetype you are building
- Know your stack (Claude / MCP / Python / platform)
- Have a TrustOps account or be ready to create one
What you need ready
- Python 3.10+ or Node 18+ (depending on kit)
- Git (to clone the scaffold)
- Model API key if using Claude or other LLM path
Where the scaffold lives
Each kit links to its scaffold in the starters/ directory of this repository. Clone or copy the subdirectory, then follow the kit page.
Kits are guided starting points, not production templates.
What TrustOps returns
- Agent ECZ-ID — your permanent identity anchor
- Credential manifest (JSON)
- API keys (issued in TrustOps) for identity injection
The Midpoint Credentialing Model
Every starter kit includes a TrustOps Credentialing Checkpoint—a designed pause point where you acquire your required ECZ-ID passports before completing integration. This midpoint approach ensures your agent is built with resolver-verifiable identity from the start, not bolted on after the fact.
10 Starter Kits for Every Agent Pattern
Each kit includes build steps, a TrustOps credentialing checkpoint, integration guidance, Resolver verification, and deploy-into-your-environment instructions.
Claude Skill Starter
Build ECZ-ID-backed skill agents using Anthropic Claude. Pre-configured with identity verification hooks, trust context injection, and struc...
Required Passports
Claude Subagent Starter
Create hierarchical subagent architectures where each subagent carries verified ECZ-ID credentials. Supports delegation chains with provenan...
Required Passports
MCP Agent Starter
Build agents using the Model Context Protocol with ECZ-ID trust anchors. Connect to any MCP-compatible model while maintaining resolver-veri...
Required Passports
API Workflow Agent
Orchestrate multi-step API workflows with ECZ-ID identity verification at every handoff. Includes retry logic, circuit breakers, and verifie...
Required Passports
Compliance & Evidence Agent
Automate compliance evidence collection and audit trail assembly. Pre-configured for common regulatory frameworks with ECZ-ID provenance anc...
Required Passports
Operations & Incident Agent
Monitor operations, detect anomalies, and coordinate incident response with resolver-verifiable identity chains. Includes alerting, escalati...
Required Passports
Support & Intake Agent
Handle inbound requests, triage tickets, and route to resolution paths with identity-aware context. Includes SLA tracking and satisfaction m...
Required Passports
Research Agent
Aggregate, cross-reference, and synthesise data from verified sources. Produces trusted research outputs with ECZ-ID provenance records and ...
Required Passports
OpenClaw / Abacus Claw Integration Starter
Integrate ECZ-ID trust infrastructure with OpenClaw and Abacus Claw platforms. Bridge identity verification into existing Claw-based agent e...
Required Passports
Generic Python Agent Starter
A minimal, unopinionated Python agent template with ECZ-ID identity hooks. Use as a foundation to build any custom agent type with resolver-...
Required Passports
From Discovery to Deployment
Every starter kit follows the same proven path.
Build
Clone the kit and complete initial setup
Checkpoint
Pause at the TrustOps credentialing checkpoint
Credential
Acquire required ECZ-ID passports in TrustOps
Complete
Return and finish integration with your credentials
Deploy
Verify through Resolver and deploy into your environment
Ready to Build Your Agent?
Choose a starter kit above, or go directly to TrustOps for credentialing.
