Agent Trust · Deployment surfaces
Agent Trust deployment surfaces
Agent Trust surfaces are being prepared across developer, repository, browser, package, and platform workflows. Public listings will appear only after the relevant core launch gates are proven. Every surface routes to TrustOps for setup and Resolver for public read-only proof.
Surface categories
This page does not list specific third-party products, marketplaces, vendors, or brand names. Each category below describes a generic class of surface where Agent Trust signals may appear once the relevant core launch gates are proven.
In preparation
Developer documentation
Public docs and routing — no setup writes, no proof clone.
In preparation
TrustOps setup
Acquisition, lifecycle, payment, and setup for credentials and bindings.
In preparation
Repository checks
Repository-side signals that read public Resolver state.
In preparation
Editor-time checks
Editor-time signals that read public Resolver state.
In preparation
Browser checks
Surface-level lookups that read public Resolver state.
In preparation
MCP / tool-call verification
Fail-closed verification path for high-risk tool calls.
In preparation
Package / verifier distribution
Verifier libraries and packages distributed for integrators.
In preparation
Platform documentation
Generic platform-side documentation that points at TrustOps and Resolver.
In preparation
Marketplace listings when approved
Listings appear only after the relevant core launch gates are proven.
This page does not claim a partnership, endorsement, marketplace approval, certification, safety guarantee, or listing availability. Public listings appear only after the relevant core launch gates are proven. All surfaces route to TrustOps for setup and to Resolver for public read-only proof.
ECZ-ID keeps setup, verification state, and public proof separated by design. TrustOps handles setup and lifecycle. Resolver remains the public proof surface.