ECZ-ID Infrastructure — Business Acquisition Gateway
For businesses, autonomous agents, regulated operators, platforms, insurers, and robotics operators.
ECZ-ID is the authoritative identity, authority, and custody infrastructure that makes your business resolver-provable, badge-linked, and machine-readable. Start with one ECZ-ID Business Passport™. Attach child passports for every domain you operate in. Badge URLs, resolver presence, and TrustOps console access are provisioned after payment confirms and backend activation completes.
This surface works for humans and agents. Machine-readable acquisition →
TrustOps exposes structured setup routes for agents, LLMs, MCP clients, procurement tools and technical buyers. Machines can read the setup manifest, analyse a URL, understand recommended ECZ-ID coverage and hand off safely into review. Payment starts setup only. After ECZ-ID Core activation and provisioning, public proof becomes available at Resolver. Full technical reference →
/api/start/manifestProduct, pricing, route and setup metadata. Opens as JSON./api/v1/url/analyseAnalyse a business, website, agent, MCP, API or software surface and return recommended setup guidance. Advisory only.{ "url": "https://example.com" }Returns corridor, trust gaps, recommended parent tier and the five recommended setup baskets. No order, no proof, no charge.
/api/agentic-checkout/intentServer-side validated review/setup handoff. The selected basket is recomputed server-side; nothing is provisioned and no proof is created.{
"basket_id": "agent_recommended",
"billing_frequency": "monthly"
}Returns a validated review handoff for human confirmation. Payment starts setup only — it is not proof.
developers.ecocitizenz.com/schemas/index.jsonPublic schemas, action descriptors and examples.GETRe-check Resolverresolver.ecocitizenz.orgRead-only public proof. Re-check before reliance.TrustOps — acquisition, setup and lifecycle
Check an ECZ-ID, domain, MCP server URL, agent manifest URL, API URL, GitHub repo, npm package, PyPI package, container image, or a public .well-known/ecz-mcp.json / .well-known/ecz-agent.json. TrustOps does not determine verification status — ECZ-ID Core controls credential state and Resolver displays public proof.
I came here to…
Pick the path that matches your visit. Each option jumps to the relevant section on this page. No chatbot, no autonomous agent, no LLM calls.
MCP and Agent Trust
ECZ-ID helps MCP providers, agent operators, developers, and enterprise teams publish and check machine-readable resolver proof before high-risk use.
TrustOps handles setup. ECZ-ID Core controls authoritative credential state. Resolver displays public proof. Verifiers and apps check, guide, and route.
Become easier for agents, tools, platforms, and enterprise teams to review, prefer, or approve under their own policy.
MCP — server, tool, and provider-side resolver posture
For MCP providers and tool operators that want to publish machine-readable resolver proof so reviewers, agents, and platforms can check the accountable operator, authorised origin, and manifest hash before high-risk tool calls.
Free
Free machine-readable checker for MCP servers, tools, and agent manifests. Use it before any high-risk tool call.
Open to all visitors
£199/mo
Help your MCP server or tool publish machine-readable resolver proof so reviewers, agents, and policy gates can check the accountable operator, authorised origin, and manifest hash.
Verified parent required
Verified parent entitlement included in this price.
£499/mo
Stronger provider-side resolver posture for MCP operators with multiple servers, regulated workloads, or higher reliance from enterprise reviewers.
Verified parent required
Verified parent entitlement included in this price.
£1,499/mo
For platforms, enterprises, and reviewers that want to express allow / warn / review / prefer / require policy against MCP and agent resolver posture under their own authority.
Assured parent required
Assured parent entitlement included in this price.
Policy gates (allow / warn / review / prefer / require) are expressed by the buyer under their own authority. ECZ-ID does not certify or approve any third-party MCP server or agent.
Agents — resolver-identifiable identity floor and KYA depth
Make your agent or operator resolver-identifiable, then strengthen Know-Your-Agent depth where reviewers, enterprises, or platforms apply stricter local policy. ECZ-ID Core controls authoritative credential state; reviewers decide.
£24.99/mo
Resolver-identifiable agent identity floor. Make your agent or operator machine-readable to reviewers so they can locate the accountable operator before high-risk tool calls.
Verified parent required
Verified parent entitlement included in this price.
£34.99/mo
Start Know-Your-Agent setup for agents and operators that need to be reviewable beyond identity floor.
Verified parent required
Verified parent entitlement included in this price.
£149.97/mo
Business-ready KYA depth for agents and operators carrying real business reliance.
Verified parent required
Verified parent entitlement included in this price.
£179.97/mo
High-reliance KYA depth for agents and operators where reviewers, enterprises, or platforms apply stricter local policy.
Assured parent required
Assured parent entitlement included in this price.
How these pieces fit together
Parent passport requirement
Declared customers may browse the catalogue. A paid parent ECZ-ID Business Passport is required before selected credentials can be activated. Verified parent access is included where shown; Assured KYA and MCP Policy require an Assured parent. TrustOps shows your order before payment — activation and resolver proof complete only after payment and provisioning.
Verified parent required for
Assured parent required for
Guided checkout builder — twelve routes
Twelve guided routes cover the headline journeys. Start guided flow asks a few short questions and builds your recommended basket. Quick review & buy skips straight to a prefilled basket if you already know what you need. Either way you review and adjust every line before checkout — no order is created until you explicitly confirm. Payment starts provisioning; payment is not proof.
Make the accountable operator of your MCP server or tool resolver-checkable before high-risk tool calls.
Give your agent an attributable, resolver-identifiable operator chain with Know-Your-Agent depth where reviewers need it.
Attach a resolver-verifiable operator and supply-chain credential chain to your API, software, model, or repository surface.
Prepare cloud-hosted operations for resolver-verifiable current-state posture and evidence review across providers.
Start one governed ECZ-ID Business Passport™ root and add the operating credentials your counterparties keep asking for.
Make your website, portal, wallet, or API machine-readable and resolver-verifiable for every counterparty interaction.
Resolver-verifiable resilience and software supply-chain credentialing tiers for repeat supplier due diligence — posture, not regulatory certification.
Prepare cyber-exposed, operationally critical and infrastructure-grade systems for evidence, posture, authority and insurer/regulator review.
Outcome-bound packs composing the exact passports for capital-release readiness or construction dispute defensibility.
Give humanoid and specialised robots attributable identity, live posture, and evidence readiness that supports insurer review.
Credential robotaxis, autonomous freight fleets, and drones with attributable identity and evidence readiness that can make underwriting review easier.
Prepare containerized cargo, marine movements, intermodal transfers and trade documentation for custody, evidence, insurer and trade-finance review.
Start from the operating context that matches your business. Each path preselects the most relevant passport family, but you can adjust the parent tier, child passports, packages, and payment method before checkout.
Give autonomous agents, APIs, and AI models a governed identity chain that platforms, counterparties, and insurers can verify.
Machine clients: GET /api/start/manifest → POST /api/v1/url/analyse → POST /api/agentic-checkout/intent → human review → card checkout.
Create your root ECZ-ID Business Passport™ and add the operating credentials your business needs for procurement, evidence, and counterparty trust.
Credential machines, vehicles, drones, and mobility assets with resolver-backed identity and governed operational state.
Build governed identity, custody, and authority infrastructure for regulated, platform-scale, or insurer-facing operations.
Enter your website URL and we'll recommend the parent tier, child passports, and packages that match your visible business surface. This is advisory only — you can adjust everything before checkout.
Or skip to browse the full catalogue manually.
Recommended basket
Everything below is editable before payment. No order is created until you review and explicitly confirm. Payment starts provisioning; payment is not proof — live state is read at Resolver after backend activation.
No route selected yet.
Pick an acquisition route and the recommended basket appears here, preselected and ready to review — or browse the full catalogue and build it yourself.
Every customer begins with one ECZ-ID Business Passport™. This is your parent identity spine — the root credential. All child passports attach to it. One identity. One resolver presence. One TrustOps context.
Your ECZ-ID Business Passport™ carries your legal identity, jurisdiction, and tier status. It is your authoritative root.
Paid business passports project a public resolver page — machine-readable, linkable, and re-checkable by any counterparty after activation. Declared previews your identity spine without a live public projection.
Your TrustOps console and Business Passport API are scoped to your identity spine. Operational dashboard and API access activate with a paid tier; Declared includes a limited preview only.
33 domain-specific child passports attach to your parent. Each inherits the authority chain from your root.
Choose the tier that matches your requirements. Verified and Assured include resolver presence, the operational dashboard, and Business Passport API access; Declared establishes a preview identity spine with limited TrustOps access. Higher tiers unlock additional child passports, badge provisioning, and enterprise capabilities.
Select Verified or Assured to activate child passports, packages and add-ons.
Declared establishes a preview identity spine and limited TrustOps access only; it does not activate child passports, packages, cloud add-ons, operational badges or Resolver-verifiable operating proof.
Browse child passports · Browse packages · View featured corridors
Featured acquisition routes
Choose a route to build an editable recommended basket. Child passports, packages and add-ons require Verified or Assured; included parent access is shown where applicable. Browse the full catalogue · Jump to child passports · Jump to packages
The trust infrastructure layer for websites, portals, and API operators. Combines a core trust baseline (Platform Safe-Harbour, Risk Policy, Identity Continuity passports) with the publishing, resolver, and reliance plumbing that makes your digital surface machine-readable, resolver-verifiable, and reliance-grade for every counterparty interaction.
Digital Counterparty Add-ons (extend your DCI baseline — selectable inline below)
Cloud add-ons help organisations structure cloud bindings, provider coverage, current-state posture, evidence references, authority timelines, and machine-readable verification routes. Setup is handled in TrustOps. ECZ-ID Core controls authoritative credential state. Resolver is read-only public proof.
Provider names identify target ecosystems only and do not imply endorsement, approval, access rights, certification, safety, insurance, compliance, security, or business quality.
Cloud option units
Configure providers, targets, actors, and entities at Review & buy. Selections within your included allowance are free setup preferences; selections beyond it add these subscription units — the price updates before you pay.
Payment starts setup. Payment does not create proof. Public proof appears only after verification completes.
Regulatory Credentialing
ECZ-ID provides resolver-verifiable vendor credentialing postures for DORA ICT risk management obligations and SBOM software liability documentation. Three tiers per product line — Essentials, Managed, and Enterprise — plus a combined Suite.
ECZ-ID is a credentialing infrastructure platform, not a supervisory authority. These packages represent vendor credentialing posture, not regulatory certification.
All tiers — Essentials, Managed, Enterprise, and the combined Suite — are available now. Pick a tier below and complete acquisition with secure card checkout. Crypto rails are in final proofing and are not available for payment today.
Digital Operational Resilience Act — ICT vendor risk management obligations for EU financial sector supply chains.
Software Bill of Materials — software composition and supply chain integrity posture for procurement and liability documentation.
Unified DORA + SBOM credentialing posture on a single locked monthly fee — combined evidence package, single-pane authority dashboard.
Commercial Outcome Packs
Two independent, outcome-bound infrastructure products. Each composes the exact passports required to produce a deterministic, resolver-verifiable commercial verdict — either capital-release readiness or dispute defensibility. Designed for repeated use across ongoing operations.
Requires a Verified or Assured parent ECZ-ID. Each pack is billed at the same cadence as your parent ECZ-ID (monthly or annual).
A clear, secure acquisition path — from selection to live credentials. Works identically for human buyers, enterprise procurement, and agent operators.
Enter your website URL for recommended starting options, or browse all corridors manually — agent, business, robotics, or enterprise. Both paths lead to the same checkout.
Choose a parent tier (Verified at £19.99/mo or Assured at £49.99/mo), then add child passports, packages, or advanced infrastructure services.
Every line item, unit price, and monthly total is shown on a transparent order review page before checkout. Nothing is charged until you explicitly proceed.
Card checkout is available now — monthly billing or an annual subscription via the card payment page. No bank direct debit, no automatic wallet debit, no token pull. Crypto rails are in final proofing and are not available for payment today; customers who need crypto can register interest.
After payment is confirmed, backend provisioning issues your ECZ-ID, activates the selected credentials, prepares your Resolver presence, and provisions badge URLs for the order. Your Resolver page and badges become authoritative only after backend activation. TrustOps shows acquisition status and next steps throughout.
Full TrustOps console, badge embed codes, public resolver URL, API credentials, and onboarding delivery to your registered email.
This is exactly what happens after your payment is confirmed. Payment starts acquisition and provisioning; backend provisioning then issues and activates your credentials. Provisioning is designed to complete quickly, but Resolver state is authoritative only after backend activation.
Your payment is confirmed and verified. Your acquisition reference is locked and your order advances to backend provisioning.
Payment confirmation starts backend provisioning. The backend — not TrustOps — issues your ECZ-ID, activates the selected credentials, prepares your Resolver presence, and provisions badge URLs for the order.
Your ECZ-ID Business Passport™ is issued at your selected tier by backend provisioning. The parent identity spine is created in the ECZ-ID infrastructure.
All selected child passports and package credentials are activated by backend provisioning and attached to your parent. Each inherits the authority chain.
Your public Resolver page becomes authoritative after backend activation. Your identity state is then provable to any counterparty, insurer, platform, or agent.
SVG trust badge URLs are provisioned for your parent and each activated credential — static, embeddable, linkable, machine-verifiable — and become authoritative once backend activation completes.
Your TrustOps console context is created. Full dashboard access: passports, ledger, evidence, authority delegation, integrations, and Business Passport API.
Login credentials, Resolver URL, badge embed codes, API keys, and onboarding documentation are delivered to your registered email address as part of the provisioned order.
Manage your credentials, submit evidence, configure authority delegation, and monitor your trust posture — all from TrustOps.
Stable reference points for what happens after you pay, where your setup documentation lives, and how renewal, repair, and revocation behave.
Payment starts setup — nothing more. ECZ-ID Core activates credentials and records authoritative state; your Resolver page is where live state is read. Counterparties should re-check at Resolver before reliance.
Product-scoped setup and binding documentation appears in your customer dashboard after purchase — cloud docs for cloud buyers, MCP docs for MCP buyers, KYA docs for agent buyers, DCI and DORA/SBOM docs for those buyers. Binding docs are not published here.
Manage passports, evidence, badges, billing, and setup from the TrustOps console. Sign in with the credentials delivered to your registered email.
If provisioning or setup stalls, your dashboard shows the order state and the next repair step. TrustOps handles acquisition repair; it never writes proof.
Subscriptions renew on their billing cadence. If a subscription lapses or is downgraded, entitlements adjust and your Resolver page reflects the current state — always re-check before reliance.
Refunds follow the published terms. Where a credential is revoked, the revoked state is what Resolver shows — badges route verifiers to that live state.
Every ECZ-ID rests on the same governed identity foundation, maintained by ECZ-ID Core.
Your root parent identity credential. Carries legal identity, jurisdiction, and tier status. The authoritative spine for all downstream credentials.
A ledger-anchored canonical state record held by ECZ-ID Core. Verified and Assured build on the same identity foundation.
Verified and Assured activation provisions the operational surfaces and trust instruments below. Payment starts setup; activation completes after ECZ-ID Core provisioning.
Domain-specific credentials (Agent Credential, Product Passport, Cyber Resilience, etc.) that attach to your parent. Payment starts setup; activation completes after ECZ-ID Core provisioning.
Embeddable SVG badge assets for every activated passport. Resolver-backed, machine-verifiable, deployable on your website, platform, or agent surface.
A dedicated public verification page that proves your identity state to any counterparty, insurer, platform, or agent. Machine-readable and human-readable.
Full operational dashboard: manage passports, submit evidence, view ledger, configure authority delegation, access Business Passport API.
Login credentials, resolver URL, badge embed codes, onboarding instructions, and next-step links delivered to your registered email.
Each child passport attaches to your parent Business Passport. Activate what you need. Each child inherits the authority chain from your root.
Child passports, packages and add-ons require a paid parent tier. Choose Verified or Assured above, then select the credentials your organisation needs.
Packages group corridor-relevant child passports into a single acquisition object at package pricing. Select a package to credential your operations faster. Package prices include the parent Business Passport at the selected tier.
Packages require a paid parent tier — choose Verified or Assured first.
15 core packages shown below. 7 enterprise accelerators available. Know-Your-Agent acquisition lives in the dedicated MCP / Agent Trust top corridor above (KYA Starter, Verified KYA Ready, Assured KYA Ready).
The Digital Counterparty Infrastructure Pack™ and the 2 Commercial Outcome Packs (Trade Finance Release, Construction Dispute Resolution) have dedicated sections above and are not duplicated in this list.
DORA and SBOM packages have moved to the dedicated DORA / SBOM credentialing section above (Essentials, Managed, Enterprise, and Suite). They are no longer presented under the legacy “Vendor Pack” / “Liability Pack” names.
Enterprise-grade infrastructure services with per-unit pricing. These services extend your ECZ-ID capabilities for specialised compliance, legal, audit, and underwriting requirements. Select to add to your order.
Each ECZ-ID mandate plate is a verification gateway, not proof in itself. Every badge links — by URL and by QR — to the entity's page on resolver.ecocitizenz.org, where the current state is resolved live. Badges are distributed by TrustOps after activation; proof is always read from Resolver.
Declared
CLICK / SCAN TO VERIFY LIVE
resolver.ecocitizenz.org
Verified
CLICK / SCAN TO VERIFY LIVE
resolver.ecocitizenz.org
Assured
CLICK / SCAN TO VERIFY LIVE
resolver.ecocitizenz.org
Active (template)
CLICK / SCAN TO VERIFY LIVE
resolver.ecocitizenz.org
Degraded (template)
CLICK / SCAN TO VERIFY LIVE
resolver.ecocitizenz.org
Revoked (template)
CLICK / SCAN TO VERIFY LIVE
resolver.ecocitizenz.org
Agent Credential
CLICK / SCAN TO VERIFY LIVE
resolver.ecocitizenz.org
Cyber Resilience
CLICK / SCAN TO VERIFY LIVE
resolver.ecocitizenz.org
API Passport
CLICK / SCAN TO VERIFY LIVE
resolver.ecocitizenz.org
AI Model
CLICK / SCAN TO VERIFY LIVE
resolver.ecocitizenz.org
Dataset
CLICK / SCAN TO VERIFY LIVE
resolver.ecocitizenz.org
IoT Device
CLICK / SCAN TO VERIFY LIVE
resolver.ecocitizenz.org
Software Supply Chain
CLICK / SCAN TO VERIFY LIVE
resolver.ecocitizenz.org
Product Passport
CLICK / SCAN TO VERIFY LIVE
resolver.ecocitizenz.org
Custody Transfer
CLICK / SCAN TO VERIFY LIVE
resolver.ecocitizenz.org
Risk Policy
CLICK / SCAN TO VERIFY LIVE
resolver.ecocitizenz.org
Industrial Robot
CLICK / SCAN TO VERIFY LIVE
resolver.ecocitizenz.org
Public-Space Robot
CLICK / SCAN TO VERIFY LIVE
resolver.ecocitizenz.org
Domestic Robot
CLICK / SCAN TO VERIFY LIVE
resolver.ecocitizenz.org
Robotaxi
CLICK / SCAN TO VERIFY LIVE
resolver.ecocitizenz.org
Autonomous Car
CLICK / SCAN TO VERIFY LIVE
resolver.ecocitizenz.org
Autonomous Haulage Truck
CLICK / SCAN TO VERIFY LIVE
resolver.ecocitizenz.org
Cross-Border Haulage Truck
CLICK / SCAN TO VERIFY LIVE
resolver.ecocitizenz.org
High-Value Cargo Truck
CLICK / SCAN TO VERIFY LIVE
resolver.ecocitizenz.org
Drone Class D1
CLICK / SCAN TO VERIFY LIVE
resolver.ecocitizenz.org
Drone Class D2
CLICK / SCAN TO VERIFY LIVE
resolver.ecocitizenz.org
Drone Class D3
CLICK / SCAN TO VERIFY LIVE
resolver.ecocitizenz.org
Drone Class D4
CLICK / SCAN TO VERIFY LIVE
resolver.ecocitizenz.org
Intermodal Transfer
CLICK / SCAN TO VERIFY LIVE
resolver.ecocitizenz.org
Industrial Site
CLICK / SCAN TO VERIFY LIVE
resolver.ecocitizenz.org
Critical Infrastructure
CLICK / SCAN TO VERIFY LIVE
resolver.ecocitizenz.org
Financial Authority — Funds Flow
CLICK / SCAN TO VERIFY LIVE
resolver.ecocitizenz.org
Marine Vessel
CLICK / SCAN TO VERIFY LIVE
resolver.ecocitizenz.org
Cargo Container
CLICK / SCAN TO VERIFY LIVE
resolver.ecocitizenz.org
Aircraft
CLICK / SCAN TO VERIFY LIVE
resolver.ecocitizenz.org
Aviation Component
CLICK / SCAN TO VERIFY LIVE
resolver.ecocitizenz.org
Platform Safe Harbour
CLICK / SCAN TO VERIFY LIVE
resolver.ecocitizenz.org
Identity Continuity
CLICK / SCAN TO VERIFY LIVE
resolver.ecocitizenz.org
Licensed Infrastructure Operator
CLICK / SCAN TO VERIFY LIVE
resolver.ecocitizenz.org
Customer-issued · Resolver-verified
Each badge below is a customer-issued example of the artwork that ships with the credential. On any badge, click or scan reaches the issued entity's page at resolver.ecocitizenz.org/p/{ECZ_ID} — that is where the live state of the credential is read. The badge does not assert the state itself; Resolver does.
Distinct from passport mandate plates. Regulatory credential badges are portrait 240×320 and carry a coloured family bar. ECZ-ID passport mandate plates remain landscape 320×120. Two artefact families, one infrastructure-grade visual language.
Customer-issued example — live proof appears only after issuance.
ECZ-ID
Regulatory Credential
Vendor Credentialing — Essentials
DORA Essentials
This entity holds active ECZ-ID credentials constituting DORA Essentials vendor credentialing posture. Resolver-verifiable.
Family code
REG-DORA-ESSENTIALS
CLICK / SCAN TO VERIFY LIVE
resolver.ecocitizenz.org
Customer-issued example
DORA Essentials
£319.96 /mo
ECZ-ID
Regulatory Credential
Vendor Credentialing — Managed
DORA Managed
Managed DORA posture with API passport, quarterly review and incident notification readiness. Resolver-verifiable.
Family code
REG-DORA-MANAGED
CLICK / SCAN TO VERIFY LIVE
resolver.ecocitizenz.org
Customer-issued example
DORA Managed
£999 /mo
ECZ-ID
Regulatory Credential
Vendor Credentialing — Enterprise
DORA Enterprise
Multi-entity DORA structural posture with enterprise API access and structured documentation for regulator and audit review. Resolver-verifiable.
Family code
REG-DORA-ENTERPRISE
CLICK / SCAN TO VERIFY LIVE
resolver.ecocitizenz.org
Customer-issued example
DORA Enterprise
£2,499 /mo
ECZ-ID
Regulatory Credential
Liability Credentialing — Essentials
SBOM Essentials
This entity holds active ECZ-ID credentials constituting SBOM Essentials liability credentialing posture. Resolver-verifiable.
Family code
REG-SBOM-ESSENTIALS
CLICK / SCAN TO VERIFY LIVE
resolver.ecocitizenz.org
Customer-issued example
SBOM Essentials
£269.96 /mo
ECZ-ID
Regulatory Credential
Liability Credentialing — Managed
SBOM Managed
Managed SBOM posture with continuous vulnerability monitoring and ingestion analytics. Resolver-verifiable.
Family code
REG-SBOM-MANAGED
CLICK / SCAN TO VERIFY LIVE
resolver.ecocitizenz.org
Customer-issued example
SBOM Managed
£899 /mo
ECZ-ID
Regulatory Credential
Liability Credentialing — Enterprise
SBOM Enterprise
Multi-product/entity SBOM structural posture with custody attestation and enterprise API access. Resolver-verifiable.
Family code
REG-SBOM-ENTERPRISE
CLICK / SCAN TO VERIFY LIVE
resolver.ecocitizenz.org
Customer-issued example
SBOM Enterprise
£2,499 /mo
ECZ-ID
Regulatory Credential
Combined Suite — Enterprise
DORA + SBOM Suite
Combined DORA + SBOM structural posture for financial-sector technology vendors. Unified resolver profile. Resolver-verifiable.
Family code
REG-DORA-SBOM-SUITE
CLICK / SCAN TO VERIFY LIVE
resolver.ecocitizenz.org
Customer-issued example
DORA + SBOM Suite
£4,499 /mo
https://resolver.ecocitizenz.org/p/<ECZ_ID>. Click and scan reach the same target. Verification happens at Resolver, not on this host.How credential badges work: Each badge is a monochrome, print-safe mandate plate that reflects your live passport state. Embed with a single <img> tag and link to your resolver page for one-click verification. All 33 child passport badges plus the parent credential are provisioned when your passports are activated.
Official Resolver Preview — example only
Resolver is the public proof surface for ECZ-ID. The card and JSON below are an illustrative preview of what an entity's Resolver page can look like — they are not a live verification. Actual identity state is always checked live at resolver.ecocitizenz.org at the moment of verification. TrustOps provisions credentials; Resolver proves them.

ECZ-ID
Public Identity Resolver
Northbridge Systems Ltd
ECZ-FR-A48N3P
Jurisdiction: GB
Passports (resolved live)
Illustrative layout — actual timestamp and state are returned by Resolver at the moment of lookup.
ECZ-ID Trust Resolution Infrastructure · Resolver = proof
// EXAMPLE OUTPUT — illustrative only.
// Live identity state is always returned by Resolver at request time.
{
"ecz_id": "ECZ-FR-A48N3P",
"entity": "Northbridge Systems Ltd",
"jurisdiction": "GB",
"tier": "<resolved live at Resolver>",
"status": "<resolved live at Resolver>",
"passports": [
{ "code": "CYBER_RESILIENCE", "status": "<resolved live>" },
{ "code": "AI_MODEL", "status": "<resolved live>" },
{ "code": "AUTONOMOUS_CAR", "status": "<resolved live>" }
],
"resolver_url": "https://resolver.ecocitizenz.org/p/ECZ-FR-A48N3P"
}Agents, platforms, and insurers fetch this JSON shape from Resolver at the moment of verification. The example above documents the field layout — actual values are always returned live by Resolver, never by TrustOps.
Agent operators and integration platforms can consume the ECZ-ID product catalogue, pricing taxonomy, SKU mappings, and deterministic acquisition endpoints as structured JSON. The manifest is the canonical machine-readable acquisition catalogue.
# Product catalogue — full taxonomy, tiers, SKUs, pricing, corridors, intent routes
# Advisory URL analysis — recommends tier/passports/packages, writes nothing
POST /api/v1/url/analyse
Body: { url } — advisory only; no identity record, resolver entry, or ledger event is created.
# Create order intent — returns checkout URL; no order without explicit confirmation
POST /api/checkout
Body: { tier, childCodes[], bundleSkus[], acceleratorSkus[], method: "card" } — card-first launch; crypto is not available for payment today
# Full API catalogue (requires auth in production)
GET /api/catalog
# Verify identity state — public proof read; re-check before reliance
GET /api/resolver/{ecz_id} — machine JSON state
GET /resolve/{ecz_id} — human-readable page
Canonical public proof host: https://resolver.ecocitizenz.org — Resolver displays public proof; TrustOps does not write canonical records. Re-check before reliance.
# Conversion intent routes — preselect the recommended basket (no auto-checkout)
/start?intent=mcp|agent|api-software|cloud|business|dci#recommended-basket
/start?intent=dora-sbom|dora-essentials|dora-managed|dora-enterprise#recommended-basket
/start?intent=sbom-essentials|sbom-managed|sbom-enterprise|dora-sbom-suite#recommended-basket
/start?intent=trade-finance|construction|critical-cyber-resilience#recommended-basket
/start?intent=robotics-insurability|mobility-insurability|global-trade-marine#recommended-basket · /start?intent=robotics#full-catalogue
Payment starts setup; payment is not proof. Proof boundary: ECZ-ID Core controls credential state, Resolver displays public proof, local policy decides.
# Guided qualification flows — short prompts → recommended basket (no provisioning, no verification, no charge in-flow)
/start?flow=mcp|agent|api-software|cloud|business|dci|dora-sbom|critical-cyber-resilience|trade-construction|robotics-insurability|mobility-insurability|global-trade-marine
# End-to-end agent acquisition flow (card-first launch)
1. GET /api/start/manifest → read product catalogue, tiers, SKUs, pricing
2. POST /api/v1/url/analyse → recommended coverage + five setup baskets (advisory)
3. POST /api/agentic-checkout/intent → server-validated review/setup handoff
4. Human confirms the basket in review → card checkout (payment starts setup only)
5. Payment webhook confirms → ECZ-ID Core activation/provisioning
6. GET /api/resolver/{ecz_id} → re-check live state; Resolver proves, local policy decides
Crypto is not available for payment today — crypto rails remain in final proofing and are not part of the active acquisition flow. Register interest in crypto payment.
Identity, authority, and custody ambiguity is the root cause of underwriting friction, platform liability, automation failure, and compliance overhead. ECZ-ID gives agents a way to make state resolver-provable and gives businesses a reusable way to meet counterparty requirements. Local policy decides how much proof each counterparty requires.
Agents without resolver-verifiable identity are harder for counterparties to rely on. ECZ-ID Agent Credential™ makes agent capability resolver-provable.
Identity and custody ambiguity is the root cause of underwriting friction. ECZ-ID makes risk attributable, portable, and machine-verifiable.
Onboarding counterparties without authoritative identity proof creates liability exposure. ECZ-ID resolves this at infrastructure level.
Machines operating in the world need machine-readable, resolver-backed identity credentials. ECZ-ID is built for this from day one.
Compliance regimes demand attributable custody chains. ECZ-ID provides the governed identity spine that supports regulator, audit and compliance review.
Product passports, custody transfer, and SBOM credentials require an authoritative parent identity. ECZ-ID is that parent.
Learn how ECZ-ID works, then acquire the Business Passport and credentials your organisation needs. Education lives at the developer site; acquisition happens here on TrustOps.
Start with one ECZ-ID Business Passport™. Attach the child passports your operations require. Pay securely. Your credentials go live once provisioning completes.
Already an ECZ-ID customer? Sign in →