ECZ-ID API Passport™
Resolver-verifiable child passport in the Digital & Operational family.
Who it is for: Businesses, platforms, and operators in APIs, AI, Data & Software, IoT & Connected Systems that need a resolver-verifiable identity for this object before counterparties, regulators, or buyers will rely on it.
In plain terms
The ECZ-ID API Passport™ is resolver-verifiable identity for an API endpoint, MCP tool, webhook, or GPT action exposed by a business.
The real-world problem
What this removes
API consumers, agents, and counterparty assessment systems often cannot resolve who operates an API, what its declared scope is, or whether the endpoint they are calling is the one the operator actually publishes.
Why this causes delay or loss
Integrations are blocked, held, or rejected when the calling system cannot resolve the API operator, scope, and current state.
Ambiguity removed
Removes ambiguity about which operator is accountable for an API endpoint and what its declared scope is.
What it binds / includes
Scope of accountability
Binds the API endpoint to its operator parent passport, declared scope, and supporting passports (AI Model, Dataset, Software Supply Chain) where applicable.
Parent requirement: Requires an active ECZ-ID Business Passport™ (Verified or Assured) to activate.
Detailed inclusions are confirmed in TrustOps. Developer Gateway documents the model only.
Typical buyers / operators
- API providers
- MCP server operators
- Platform / SaaS operators
- Agent dependency owners
Pre-mandate value
Lets agent operators and counterparties resolve API identity and scope before integration.
Stack contributions
What PulseGuard™, LedgerCore™, and Resolver contribute
PulseGuard™
PulseGuard™ contributes present-state monitoring such as liveness, freshness, revocation or suspension state, and posture changes where supported by the activated passport/package.
LedgerCore™
LedgerCore™ records decisive lifecycle and evidence events where supported, such as issuance, activation, authority changes, child passport creation, revocation, bundle activation, badge state changes, or receipt references.
Resolver
Resolver shows the API operator, declared scope, attached supporting passports, and current passport state.
Badge / mandate plate
Where this product has an ECZ-ID badge or mandate plate, the badge is an embeddable visual pointer to the Resolver state. The badge is not proof by itself; the Resolver check is the proof surface.
Insurability Readiness™ impact
Insurability Readiness™ is derived, free, non-sellable, and not manually editable. It is earned from the active passport stack, PulseGuard state, and LedgerCore evidence where supported. You do not buy readiness; you earn it.
Boundary of claim
What this product does not claim
- · Does not certify the API is free of vulnerabilities.
- · Does not monitor API request payloads, prompts, or user data.
- · Does not constitute regulator approval of the endpoint.
Guided flow
Six steps from need to resolved state
- 01
Understand the need
Decide what commercial friction you are trying to remove. Developer Gateway documents the model. It does not determine eligibility, issue credentials, or create entitlements.
- 02
Confirm parent requirement
Every child passport, package, and add-on attaches to an active ECZ-ID Business Passport™. Verified or Assured may be required (per TrustOps).
- 03
Review what this product does
Check what is bound, what is included, and what it does not claim. No safety, certification, approval, or partnership claim is made on this page.
- 04
Continue to TrustOps
Acquisition, activation, payment, and lifecycle happen in TrustOps. Developer Gateway only routes the handoff.
- 05
Return to Developer Gateway
After TrustOps, return here for next-step docs and related guidance. Developer Gateway still does not prove current state.
- 06
Check current proof in Resolver
Current proof must be checked in the public Resolver. Copied metadata, screenshots, or website claims do not replace Resolver.
TrustOps midpoint
Acquisition, setup, payment, and lifecycle happen in TrustOps
Developer Gateway only routes. It does not host checkout, change canonical state, issue credentials, or replace Resolver proof. TrustOps owns the operational state for this product.
Browse child passports in TrustOps ↗TrustOps URL: https://trustops.ecocitizenz.com/start
Return path
Come back here for next-step docs
After TrustOps completes acquisition or activation, return to Developer Gateway for related docs and guided next steps. Developer Gateway still does not prove current state. Current proof remains in Resolver.
Resolver proof
Current proof must be checked in Resolver
Copied metadata, screenshots, badges on third-party websites, or any claim made on Developer Gateway do not replace Resolver. The Resolver is the sole public proof surface for ECZ-ID.
Open Resolver ↗Resolver URL: https://resolver.ecocitizenz.org
Recommendation
Find your recommended starting point
Enter your website URL. TrustOps will use it to recommend a starting point. Developer Gateway sends the URL only; TrustOps handles the recommendation, setup, payment, and lifecycle controls.
Developer Gateway does not host checkout, change canonical state, issue credentials, or replace Resolver proof. Current proof must be checked in Resolver.