EcoCitizenZ
← All Starter Kits
Advanced2-3 hoursOpenClaw / Abacus Claw · Python

OpenClaw / Abacus Claw Integration Starter

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

1Get starter scaffold2Install dependencies3Go to TrustOps /start4Paste credentials5Run locally6Verify via Resolver7Deploy into your environment

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 bridge integration connecting ECZ-ID trust infrastructure with OpenClaw and Abacus Claw agent ecosystems. This produces a resolver-verifiable identity layer within existing Claw-based deployments, enabling cross-platform identity mapping and resolver-verifiable agent operations.

2Who It Is For

Teams already using OpenClaw or Abacus Claw platforms who need to add resolver-verifiable identity infrastructure. Ideal for organisations extending existing Claw-based agent deployments with ECZ-ID trust anchoring.

3Why ECZ-ID Matters Here

Claw ecosystems provide powerful agent capabilities but lack native identity verification infrastructure. ECZ-ID bridges this gap, giving every Claw-based agent a resolver-verifiable identity that works across platform boundaries.

4Architecture

Claw Platform Connector

Native integration with OpenClaw and Abacus Claw platform APIs and agent lifecycle management.

ECZ-ID Trust Bridge

Maps Claw platform identities to ECZ-ID resolver-verifiable identities, maintaining both identity systems.

Cross-Platform Identity Mapper

Bidirectional identity mapping between Claw ecosystem IDs and ECZ-ID resolver-verifiable identities.

Trust Anchor Injector

Injects ECZ-ID trust anchors into Claw agent operations without modifying core Claw logic.

Claw Ecosystem Adapter

Adapts ECZ-ID verification patterns to work within Claw platform conventions.

Dual Audit Logger

Produces audit trails compatible with both Claw platform logging and ECZ-ID provenance chains.

5Build Steps Overview

1
Clone the OpenClaw integration starter
Pull the template with Claw platform integration scaffolding.
2
Install dependencies
Install the ECZ-ID SDK, Claw platform SDKs, and bridge connectors.
3
Configure Claw platform access
Set up connections to your OpenClaw or Abacus Claw environment.
4
Map existing identities
Identify which Claw agents need ECZ-ID resolver-verifiable identities.
5
Review bridge patterns
Understand how the identity bridge works before credentialing.

Trust Map

Required Passports
ECZ-ID Business PassportAgent CredentialAPI Passport
Recommended Passports
Software Supply Chain PassportAI Model Passport
Relevant Packages
KYA Ready Pack™Developer Payout Pack
What Each Enables
ECZ-ID Business Passport: Organisation identity for the Claw-integrated agent fleet
Agent Credential: Verified bridge identity for cross-platform operations
API Passport: Evidence-linked handoffs between Claw and ECZ-ID ecosystems
AI Model Passport: Model provenance verification within Claw agents

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
  • API Passport

Recommended Passports

  • Software Supply Chain Passport
  • AI Model Passport

Relevant Packages

KYA Ready Pack™Developer Payout Pack

What You Must Acquire in TrustOps

ECZ-ID Business Passport
Enables: Parent identity for your Claw-based agent fleet
Agent Credential
Enables: Resolver-verifiable identity for the bridge integration agent
API Passport
Enables: Verified API handoffs between Claw and ECZ-ID ecosystems
AI Model Passport (recommended)
Enables: Verification of models used within the Claw ecosystem

What You Bring Back from TrustOps

Bridge Agent ECZ-ID
Resolver-verifiable identity for the integration bridge
Agent ECZ-IDs
Resolver-verifiable identities for each Claw agent being bridged
API Keys
Production ECZ-ID API keys for the bridge integration
Identity Mapping Config
Configuration for Claw-to-ECZ-ID identity mapping
Continue in TrustOpsView Required ECZ-ID Package

9Return and Complete Integration

With your TrustOps credentials in hand, return here to complete the final build steps.

1
Inject bridge credentials
Add bridge Agent ECZ-ID and API keys to the integration configuration.
2
Map Claw agents to ECZ-IDs
Configure the identity mapping between existing Claw agents and their ECZ-IDs.
3
Enable trust anchor injection
Activate ECZ-ID trust anchoring within the Claw agent pipeline.
4
Test cross-platform flows
Verify identity flows across the Claw-to-ECZ-ID bridge in sandbox.
5
Validate dual audit
Confirm audit trails are produced in both Claw and ECZ-ID formats.

10Verify Through Resolver

Verify bridge identity

Query the bridge agent’s ECZ-ID through Resolver.

Verify Claw agent via ECZ-ID

Look up any Claw agent’s ECZ-ID resolver-verifiable identity through Resolver.

Trace cross-platform flows

Follow an agent action from Claw through the ECZ-ID bridge via Resolver.

Validate identity mapping

Confirm bidirectional identity mapping is consistent and correct.

Verify with Resolver

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.

Alongside existing Claw deployments
Cloud environments (AWS, GCP, Azure)
Kubernetes clusters
Docker containers
Hybrid Claw + ECZ-ID environments
Multi-platform agent orchestration

12Limits & Non-Claims

  • This kit does not provision credentials. All credentialing happens through TrustOps.
  • This kit does not replace Claw platform functionality. It adds an identity verification layer.
  • Claw platform access and licensing are separate requirements.
  • Identity mapping requires both Claw platform admin access and ECZ-ID credentials.
  • Performance overhead depends on Claw platform configuration.

Ready to Build This Agent?

Start with the build steps above, credential through TrustOps, and deploy your resolver-verifiable agent anywhere.

Continue in TrustOpsView All Starter Kits