# 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 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 - /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 - /agent-trust/mcp-verifier/ MCP Verifier install + usage (npm @ecocitizenz/ecz-id-mcp-verifier@0.7.0) - /agent-trust/github-action/ GitHub Action usage (Marketplace Ecocitizenz/ecz-id-mcp-verifier@v0.7.1) - /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 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) 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, 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. - 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