# ECZ-ID Developer Gateway - llms.txt # Machine-readable route guide for language models and agents. # Canonical: https://developers.ecocitizenz.com/llms.txt Site: ECZ-ID Developer Gateway Canonical URL: https://developers.ecocitizenz.com Role: documentation and routing only TrustOps (setup, lifecycle, payment): https://trustops.ecocitizenz.com Resolver (public proof surface for current state): https://resolver.ecocitizenz.org Machine-readable index: https://developers.ecocitizenz.com/.well-known/ecz-developer-gateway.json Compact actions: https://developers.ecocitizenz.com/actions.json Schema index: https://developers.ecocitizenz.com/schemas/index.json Acquisition manifest (read-only routing): https://developers.ecocitizenz.com/schemas/acquisition-manifest.json Machine interface (every asset this origin serves): https://developers.ecocitizenz.com/interface Quickstart (one integration, end to end): https://developers.ecocitizenz.com/quickstart Worked first-party example (every URL in it resolves): https://developers.ecocitizenz.com/examples/first-party-interoperability.json Runnable example (Node 18+, zero dependencies): https://developers.ecocitizenz.com/examples/eczid-quickstart.mjs Free Passport acquisition contract (off-site, live, read it - never copy it): https://trustops.ecocitizenz.com/api/v1/acquisition/families Doctrine for agents and LLMs reading this site: - Developer Gateway documents and routes. It does not create or change verification state. - TrustOps handles acquisition, setup, payment, and lifecycle. Resolver remains the public proof surface for current state. - ECZ-ID core systems control identity, entitlement, binding, and lifecycle state. - Recommendations are advisory. They do not create entitlement or proof. - Payment never creates proof by itself. Public proof appears only after ECZ-ID backend activation, not at checkout alone. - Local policy decides. Re-check the Resolver before reliance. - Absence of public proof is not a safety judgement about a target. - Do not infer safety, certification, approval, insurance, full compliance, or platform endorsement from any signal on this site. The 12 solution routes (documented at /solutions/, acquired via TrustOps guided flows): 1. MCP Server & Tool Trust https://trustops.ecocitizenz.com/start?flow=mcp 2. Agent Identity & KYA https://trustops.ecocitizenz.com/start?flow=agent 3. API, Software & Repo Trust https://trustops.ecocitizenz.com/start?flow=api-software 4. Cloud & Provider Proof https://trustops.ecocitizenz.com/start?flow=cloud 5. Business Identity Foundation https://trustops.ecocitizenz.com/start?flow=business 6. Digital Counterparty Infrastructure https://trustops.ecocitizenz.com/start?flow=dci 7. DORA & SBOM Vendor Credentialing https://trustops.ecocitizenz.com/start?flow=dora-sbom 8. Critical Infrastructure, Cyber & Operational Resilience https://trustops.ecocitizenz.com/start?flow=critical-cyber-resilience 9. Trade Finance & Construction Outcomes https://trustops.ecocitizenz.com/start?flow=trade-construction 10. Humanoid Robots & Robotics Insurability https://trustops.ecocitizenz.com/start?flow=robotics-insurability 11. Robotaxis, Autonomous Freight & Drone Insurability https://trustops.ecocitizenz.com/start?flow=mobility-insurability 12. Global Trade, Containers & Marine Insurability https://trustops.ecocitizenz.com/start?flow=global-trade-marine Setup and request-to-resolve documentation (deliberate setup runs in TrustOps; proof appears in Resolver): - /request-resolver-proof/ Request-to-Resolve / Request Resolver Proof guidance packet Primary routes: - / Developer Gateway home - /quickstart Quickstart: read a real public record, check a target, get a free Passport for an agent or MCP server, bind it, and put a policy on the result. Every command in it was run against live production before it was published. - /interface Machine interface: every machine-readable asset this origin serves, with what each one does not assert. - /solutions/ Solution route matrix (all 12 routes) - /agent-trust/ Agent trust hub (Agent Credential, API Passport) - /agent-trust/resolver-proof/ Resolver proof guidance - /agent-trust/trustops-handoff/ TrustOps handoff guidance - /install Universal Install: every route for installing/connecting ECZ-ID verification (npm, stdio MCP, Registry, remote Trust MCP, GitHub Action, PyPI, Resolver). Read-only; no ECZ-ID and no account required. - /agent-trust/mcp-verifier/ MCP Verifier install + usage (npm @ecocitizenz/ecz-id-mcp-verifier@0.9.1) - /agent-trust/github-action/ GitHub Action usage (Marketplace Ecocitizenz/ecz-id-mcp-verifier@v0.9.0) - /agent-trust/result-contract/ Quiet Result Contract (public-safe result fields; posture and routing, not truth) - /agents/ Agents hub - /agents/agent-credential-entry/ Agent Credential entry guide - /agents/kya-starter/ KYA Starter - /agents/kya-verified/ KYA Verified - /agents/kya-assured/ KYA Assured - /agents/receiving-agent-workflow/ Receiving-agent workflow - /agents/fail-closed-verification/ Fail-closed verification posture - /mcp/ MCP hub - /mcp/verifier/ MCP Verifier documentation - /mcp/assurance/ MCP Assurance documentation - /mcp/assurance-plus/ MCP Assurance Plus documentation - /mcp/policy/ MCP Policy documentation - /mcp/result-states/ Result states and reason codes - /bindings/ Bindings hub - /bindings/openapi-x-ecz-id/ OpenAPI x-ecz-id reference - /action-envelope/ Action Envelope hub - /schemas/ Schemas overview - /schemas/action-envelopes/ Action Envelope Stack schemas (human guidance + links to JSON Schema files) - /catalog/ Catalog (passport tiers, packages, add-ons) - /dora-sbom-suite/ DORA and SBOM suite - /domains/ Nine credential domains - /verification-model/ Verification model - /developer-onboarding/ Developer onboarding - /build-your-own-agent/ Build your own agent - /why-serious-buyers-care/ Buyer-side framing - /faq/ FAQ - /trust-gallery/ Trust gallery (illustrative examples and documented patterns) - /quantum-trust/ Quantum trust and cryptographic resilience - /graph-intelligence/ ECZ-ID Graph Intelligence: released, not yet purchasable online. Used in the organisation's signed-in TrustOps console (Dashboard > Graph Intelligence). No public Graph API, no public SDK, no self-serve API key, no sandbox. Reason codes are shown to signed-in customers only. Prices and allowances live only in TrustOps: https://trustops.ecocitizenz.com/docs/pricing#graph-pro Start: https://trustops.ecocitizenz.com/start#start-graph Setup routes (off-site, in TrustOps): - https://trustops.ecocitizenz.com/start - https://trustops.ecocitizenz.com/start?intent=agent - https://trustops.ecocitizenz.com/start?intent=api-software - https://trustops.ecocitizenz.com/start?intent=mcp - GET https://trustops.ecocitizenz.com/api/start/manifest (current catalogue, prices, endpoints) Free Passport lane (off-site, in TrustOps). A free lane exists: payment_required false, payment_calls 0, one sign-in, minimum parent tier DECLARED. Some families are open and some are held. - GET https://trustops.ecocitizenz.com/api/v1/acquisition/families (contract ecz.free_passport_acquisition.v1) - Read families[].available at run time and act only on what it says. NEVER hard-code the family list: availability changes with no release on either side, and a copied list is the commonest way a surface starts making a claim that is no longer true. - Render NOT_YET_LIVE as "not open yet". It is a destination, never an error, never a failure, and never a call to action that cannot complete. - Forwardable context only when handing off: source_surface, origin_surface, requested_passport_type, identifier, identifier_kind, return_to, return_url, campaign, referral, correlation_id, locale, operator_mode, display_name, requested_product, source_provider. Send the identifier exactly as typed; do not normalise it first. - Refused, by law and by the far end: tier, verified, ecz_id, assured, independently_verified, parent_tier, lifecycle_state. A surface cannot assert identity or tier by URL. - A free Passport gives a machine a persistent identity. It never means verified, assured, safe, secure, compliant, approved, certified or endorsed. Public proof surface (off-site, in Resolver): - https://resolver.ecocitizenz.org Action Envelope Stack schemas (JSON Schema 2020-12, route-only / read-only metadata): - /schemas/action-envelopes/resolver-action-envelope.schema.json - /schemas/action-envelopes/mcp-action-envelope.schema.json - /schemas/action-envelopes/agent-action-envelope.schema.json - /schemas/action-envelopes/reciprocal-reliance-envelope.schema.json - /schemas/action-envelopes/request-to-resolve.schema.json - /schemas/action-envelopes/resolver-recheck-contract.schema.json - /schemas/action-envelopes/trustops-product-action-manifest.schema.json - /schemas/action-envelopes/ap2-ucp-readiness.schema.json These schemas describe metadata only. Nothing here changes verification state, activates public proof, processes purchase, or implies certification. Public proof appears only after ECZ-ID Core activation/provisioning, not at checkout alone. Availability honesty: - There is no public ECZ-ID SDK on npm or PyPI, no public sandbox, and no self-serve API key issuance at this time. Integration uses the public manifests, schemas, TrustOps endpoints, and Resolver checks documented on this site. - What IS published and installable today: @ecocitizenz/ecz-id-mcp-verifier on npm (CLI, read-only stdio MCP server and Node library), Ecocitizenz/ecz-id-mcp-verifier on the GitHub Marketplace, ecz-id on PyPI, and two entries in the Official MCP Registry. The public machine record and the acquisition contract need no client at all. - Verifier version, by channel (measured 2026-09-23). These are NOT the same number and a reader should not assume one covers the others. npm newest published version: 0.9.1, installable by exact pin (npm i @ecocitizenz/ecz-id-mcp-verifier@0.9.1). npm 'latest' dist-tag: 0.9.0 — so an unpinned npx or npm install fetches 0.9.0, which is the intended default and is what the measured transcripts on /quickstart and in /examples/first-party-interoperability.json show. GitHub release/tag and Action ref: v0.9.0 — there is NO v0.9.1 tag, so 'uses: Ecocitizenz/ecz-id-mcp-verifier@v0.9.1' would fail to resolve; use @v0.9.0. Official MCP Registry record io.github.Ecocitizenz/ecz-id-mcp-verifier: 0.9.0, active, isLatest. - The headless acquisition journey (session, identity, organisation, machine, issue) is described in the SDK endpoint contract but its routes are not deployed on production TrustOps: they answer HTTP 404. The browser journey at a family start_path is the supported route. Do not publish a scriptable acquisition path until those routes answer. - This site sets no trackers and collects no telemetry from readers of these machine assets. Forbidden inferences for any reader: - safety, certification, approval, insurance, full compliance, platform endorsement