Reference

Passport model

The Business Passport and the seven family Passports as the TrustOps acquisition contract defines them: subject law, identifier kinds and publish kit.

Live · public

Live in production and publicly readable, with no account and no key. Measured read-only on 2026-10-10.

Contract: Core contractDefined and held by ECZ-ID Core. Documented so you can integrate; Core serves no public schema or endpoint for it.
Machine-readable: A live Business Passport record (opens in a new tab)

Accountability Chain:Identity

Source contract

Family facts on this page come from ecz.free_passport_acquisition.v1 at https://trustops.ecocitizenz.com/api/v1/acquisition/families (opens in a new tab), snapshot read 2026-10-09. Read the contract itself before you automate against it; availability is deliberately not copied here.

Subject law

Family	One Passport is	Never a new Passport
Agent	one logical AI agent operated by the Parent	version, deployment, replica, region, platform
MCP	one logical MCP server operated by the Parent	tool, endpoint, deployment, replica
Plugin	one logical plugin / extension / integration artefact published by the Parent, independent of the marketplace it is listed on	version, release, install, execution, store_listing, skill_component, action_run, workflow_reference
API	one authorised API surface operated by the Parent	version, environment, regional_alias, gateway
IoT	one physical device (or one device identity module) operated by the Parent	mac_address, ip_address, firmware_version, gateway, hub_registration
SDK	one logical library/SDK published by the Parent, across languages and registries	version, release, registry_channel, package_artefact
Service & Workload	one ENDURING logical service or workload operated by the Parent; never a pod, replica, instance, process or region; provider-neutral continuity	pod, replica, instance, process, deployment_instance, region, cluster, runtime_credential

Identifier kinds

Family	Identifier kinds accepted at acquisition
Agent	`a2a_card_url` (the agent's A2A card URL); `well_known_origin` (the origin publishing the agent's .well-known manifest); `repository` (host/owner/repo of the source repository); `package` (ecosystem:name of the published package (no version))
MCP	`mcp_endpoint` (the MCP server endpoint URL); `registry_server_name` (the MCP Registry server name, e.g. com.ecocitizenz/trust-mcp); `repository` (host/owner/repo of the source repository); `package` (ecosystem:name of the published package (no version))
Plugin	`plugin_name` (publisher-namespace/plugin-name as declared in the manifest); `plugin_manifest_url` (the URL of the plugin manifest); `repository` (host/owner/repo of the source repository); `package` (ecosystem:name of the published package (no version))
API	`api_base_url` (the API base URL; a trailing /vN version segment is a binding, not the subject); `openapi_url` (the URL of the OpenAPI document); `repository` (host/owner/repo of the source repository)
IoT	`device_serial` (PLAIN over the composite manufacturer:model:serial; hash only); `device_attestation_ref` (SoC identity / attestation reference where the platform provides one; hash only)
SDK	`repository` (host/owner/repo of the source repository); `package` (ecosystem:name of the published package (no version)); `sdk_name` (publisher-scoped logical name when neither repository nor package is public)
Service & Workload	`workload_name` (stable publisher-scoped logical name, e.g. payments/ledger-writer); `service_origin` (the workload's primary origin where one exists); `repository` (host/owner/repo of the source repository)

Publish kit

Every family shares the record at `/p/{ecz_id}` on the Resolver, the machine record at `/api/p/{ecz_id}.json`, and a child badge and QR served by TrustOps.
Family	Where to embed the ECZ-ID
Agent	.well-known/ecz-agent.json pointer; ecz_id + resolver_backlink in the agent card
MCP	.well-known/ecz-mcp.json; MCP Registry pointer; A2A publication (C12)
Plugin	ecz_id + resolver_backlink in the plugin manifest (.claude-plugin, .cursor-plugin, .codex-plugin, package.json, action.yml)
API	OpenAPI info: x-ecz-id + x-ecz-resolver-backlink
IoT	device label QR -> /p/{ecz_id}; fleet manifest field
SDK	package.json ecz_id/resolver_backlink; pyproject.toml [tool.ecz_id]; README badge
Service & Workload	workload manifest / deployment annotation ecz_id + resolver_backlink; trust-graph node workload

Parent tiers

`parent_tier`	Meaning
`DECLARED`	Self-declared organisation identity. Not independently verified. The minimum for every free family.
`VERIFIED`	The organisation’s identity is verified. Its machines are not.
`ASSURED`	The highest parent tier. Its machines are still not verified by it.

This page is explanation, not authority. Current state is only ever the live Resolver record. Live facts on this page were measured read-only on 2026-10-10.