EcoCitizenZ
HomeBinding RegistryRequest-to-Resolve
Workflow · Request-to-Resolve

Request-to-Resolve

Ask a counterparty to obtain or prove an ECZ-ID parent tier, passport, package, or binding. Proof appears only when Backend/Core verifies and Resolver projects.

Why send a Request-to-Resolve

  • Before agent access — before allowing an external agent to act inside your system.
  • Before API integration — before integrating with a counterparty API.
  • Before supplier onboarding — before adding a new supplier into procurement.
  • Before payout — before releasing funds to a counterparty.
  • Before procurement — before issuing a procurement decision or contract.
  • Before SBOM review — before accepting an SBOM/release into a review pipeline.

What a request can ask for

  • A required parent tier (Declared / Verified / Assured).
  • Specific passports (Agent Credential, API Passport, ...).
  • Specific packages or bundles.
  • Specific bindings (domain, agent, API, MCP, SBOM).
  • A short reason or message for the counterparty.
  • An expiry timestamp on the request itself.
  • A return target so the requester is notified once Resolver state changes.

Request payload example

This is the canonical shape of a Request-to-Resolve payload. Developer Gateway does not host a live request form; the link routes to TrustOps and the proof appears in Resolver.

Request payload (illustrative)
{
  "request_type": "request-to-resolve",
  "required_parent_tier": "Verified",
  "requested_passports": ["AGENT", "API"],
  "requested_packages": ["KYB-GATE-PACK"],
  "requested_bindings": ["domain", "agent", "api"],
  "reason": "Vendor onboarding for example.com",
  "expires_at": "<timestamp>",
  "return_target": "https://requester.example.com/onboarding/return"
}

What happens next

  • The requester sends the request link to the counterparty.
  • The counterparty enters TrustOps to acquire or complete the requested binding.
  • Backend/Core verifies once control evidence is observed.
  • Resolver projects the BOUND state when verification completes.
  • The requester verifies the result against Resolver — never against a forwarded screenshot.

Free vs advanced

  • A basic request link is free.
  • Branded, bulk, or workflow features are paid only where the package supports them.
  • No live request form is hosted on Developer Gateway. There is no checkout here.
ECZ-ID keeps setup, verification state, and public proof separated by design. TrustOps handles setup. Resolver remains the public proof surface. Re-check before reliance.