ECZ-ID AI Agent Inspection

ecz-id-agents statically inspects AI agent manifests for ECZ-ID configuration posture and declared relationships (tools, APIs, MCP servers, operator/principal). Part of the ECZ-ID PyPI family. It inspects, explains and routes only.

It never imports or executes agent code, never loads or runs agent tools, and never reads prompts into results — only their presence is noted, and redaction guards every export. It never issues or activates an ECZ-ID, never prices or carts, and never certifies. It is not a safety/compliance/insurance/premium decision and not a behavioural, alignment, capability or safety proof about the agent. Missing public proof is neutral. Local policy decides. Re-check before reliance.

One-command first run

$ ecz-id-agents inspect ./my-agent
ECZ-ID inspection: ./my-agent [ecz-id-agents]
A. configuration posture : PRESENT
B. public proof posture  : NOT_CHECKED  (neutral)
...
local policy decides; re-check before reliance

Supported inputs

• A directory or manifest file. Recognised structured surfaces (static JSON only): agent_manifest.json, agent.json, agents.json, A2A Agent Cards (.well-known/agent-card.json, .well-known/agent.json), ecz-agent.json (and .well-known/), and agent-plugin descriptors (ai-plugin.json, agent-plugin.json).
• Prose surfaces — AGENTS.md and SKILL.md — are recorded by presence and location only. Their content is instruction text written for an agent, so it is never opened, never parsed and never summarised into a result.
• Observes declared agent name, model provider, tool / API / MCP / package / repository relationships and the declared operator / principal.

Evidence classes

Discovered facts are kept in separate classes so one can never be read as another:

These files do not establish verified identity, operator or authority. They record what a subject declares about itself; independent proof is a separate step, and the Resolver remains the read-only source of public proof. Credential posture is key names only — values are never read into a result.

Runtime object inspection (adapter boundary)

For OpenAI Agents, Pydantic AI, LangGraph and CrewAI, you may pass an already-constructed object and get neutral observations back — attributes are read, never called, the framework is identified without importing it, tools are not executed, and prompts are never inlined:

from ecz_id_agents import inspect_agent_object

report = inspect_agent_object(my_agent)   # {"observations": [...], "note": "..."}

Privacy boundaries

Static JSON inspection; never imports or executes agent code. Bounded, symlink-refusing enumeration. No telemetry, no uploads. Prompts are never inlined; secrets redacted on every export. Offline mode (--offline / ECZ_ID_OFFLINE=1) skips all network.

Explicit non-claims

Not a safety / certification / compliance / insurance / premium decision. Not a behavioural, alignment, capability or safety proof. Does not issue, activate or bind an ECZ-ID. Does not upload prompts. Does not price or cart.

Python API

from ecz_id_agents import inspect

result = inspect("./my-agent")
print(result.configuration_evidence.posture.value)   # PRESENT / PARTIAL / ABSENT / INVALID

CI / test example

$ ecz-id-agents inspect . --json > ecz-id-agents.json   # exit 0 for any completed inspection
$ ecz-id-agents doctor --json

Routes

• Resolver: https://resolver.ecocitizenz.org
• TrustOps: https://trustops.ecocitizenz.com/start
• Developer Gateway: https://developers.ecocitizenz.com
• Central Machine Interface: https://machine.ecocitizenz.org/.well-known/ecz-machine.json

Agent Credential and Know-Your-Agent guidance is arranged via TrustOps — this package only routes you there.

Re-check

$ ecz-id-agents recheck ./my-agent --json

Machine-readable integration

Machine Interface · Manifest · Resolver · Operator setup · Developer guidance

Each installation includes structured machine-readable metadata for automation, CI and supported integrations. Every JSON report embeds a compact machine_interface object with the canonical roots and safe, read-only actions.

The package runs locally to inspect, explain and route. It does not issue an ECZ-ID, write canonical truth, create public proof, price a cart, or replace Resolver proof.

$ ecz-id-agents manifest --json
$ ecz-id-agents compare ./old ./new --json    # neutral drift
$ ecz-id-agents inspect . --sarif             # SARIF for code scanning
$ uvx ecz-id-agents inspect .                 # or: pipx run ecz-id-agents inspect .

• Central Machine Interface: https://machine.ecocitizenz.org/.well-known/ecz-machine.json
• Resolver (read-only public proof): https://resolver.ecocitizenz.org
• Operator setup (TrustOps): https://trustops.ecocitizenz.com/start
• Developer Gateway: https://developers.ecocitizenz.com

Need help choosing the right ECZ-ID route?

Use ECZ-ID GPT guidance: https://trustops.ecocitizenz.com/start#gpt-guidance

Route guidance only. TrustOps handles setup; Backend/Core writes truth; Resolver proves public state. Local policy decides reliance. Re-check before reliance.

Continue with ECZ-ID

• Operator setup: https://trustops.ecocitizenz.com/start
• Developer guidance: https://developers.ecocitizenz.com
• Public Resolver proof: https://resolver.ecocitizenz.org
• Central Machine Interface: https://machine.ecocitizenz.org/.well-known/ecz-machine.json
• EcoCitizenz: https://www.ecocitizenz.com
• Specifications and governance: https://www.ecocitizenz.org
• ECZ-ID on Visual Studio Marketplace: https://marketplace.visualstudio.com/publishers/ecocitizenz
• ECZ-ID on Open VSX: https://open-vsx.org/namespace/ecocitizenz
• Explore the ECZ-ID Python tool family: https://pypi.org/search/?q=ecz-id

Licence and trademarks

Apache-2.0 (see LICENSE, NOTICE). The code licence grants no trademark rights; “ECZ-ID” and “EcoCitizenz” are trademarks of their owner(s) — see TRADEMARKS.md. Changelog: CHANGELOG.md. Security: SECURITY.md.

CLI: ecz-id-agents  |  Import: ecz_id_agents  |  Plugin group: ecz_id.plugins