Agent
FreeOne logical AI agent operated by the organisation.
Agent estate ↗BUSINESS PASSPORT
The ECZ-ID Business Passport establishes the organisation identity that the seven canonical machine-surface Passports sit under. Start free with Declared, then use Verified or Assured where the reliance context needs stronger organisation verification.
ONE PARENT. SEVEN FREE MACHINE-SURFACE PASSPORTS.
The Business Passport does not create blanket authority, safety, compliance or approval for everything the organisation operates. Each machine surface gets the canonical Passport that matches what it actually is.
One logical AI agent operated by the organisation.
Agent estate ↗One logical MCP server operated by the organisation.
MCP estate ↗One logical plugin, extension or integration artefact published by the organisation.
Plugin estate ↗One authorised API surface operated by the organisation.
API estate ↗One physical device or device identity module operated by the organisation.
IoT estate ↗One logical library or SDK published by the organisation.
SDK estate ↗One enduring logical service or workload—not a pod, replica, process or region.
Workloads estate ↗BUSINESS PASSPORT TIERS
Begin with an organisation identity and ECZ-ID parent context.
Start Free ↗For reliance contexts that need stronger organisation verification.
View Verified →For higher-assurance organisation identity and more demanding reliance contexts.
View Assured →Annual subscription options, where available, are shown through the purchase path. No USDC checkout availability is implied here.
PROOF BOUNDARY
Core determines canonical ECZ-ID state. TrustOps handles acquisition and lifecycle. Resolver exposes the relevant published proof state. Authority, delegation, Intent, current-state checks, decisions, Receipts and evidence remain distinct layers and should never be inferred merely from holding a Passport.