Use Mirror Surfaces

How the Use Mirror portal surfaces map to SDK acquisition, first hosted calls, workflow composition, and key ownership

Use this page when you want the shortest answer to: which Portal surface should I open first?

Download the current built artifacts from Develop → SDK and choose the right integration mode.

Run the first hosted request against the current service credential plus bearer token contract.

Compose a full protected workflow across agent registry, MCP registry, policy, retrieval, connectors, and hosted runtime calls.

Generate prompt, vector, signing, session, and FHE rails and export or hand off the right material to KMS.

What each surface is for

Portal surface	Primary job	Backing contract
`SDK` (`Develop → SDK`)	acquire the right built artifact from the entitlement-aware SDK catalog	entitlement-aware release bundle
`Onboarding`	guided SDK setup, env blocks, and starter examples	service credential plus SDK bundle
`Playground`	prove the hosted runtime path works	service credential plus bearer token
`Builder`	assemble a multi-step protected workflow	hosted products and delegated/runtime flows
`Key Management`	generate and export customer-owned keys, plus session/KMS rails	offline license and hosted session/KMS rails

Use Mirror is the operator-facing entry point. Start there before drilling into deep SDK or API reference pages.

Check licensed products in Account Settings or Billing & Usage, or read Entitlements and Access.
Create a service credential.
Open Develop -> SDK and download the licensed package bundle, or download the service-credential handoff bundle from Develop -> Credentials during create/rotate.
Install the right artifact from the bundle.
Open Use Mirror -> Onboarding or Use Mirror -> Playground and run the first hosted call.

Check licensed products in Account Settings or Billing & Usage, or read Entitlements and Access.
Confirm the enterprise has a Local SDK License for offline/native use.
Open Key Management to generate or export the right rails.
Install the native artifact from artifacts/*.

Start with Builder when the workflow spans hosted runtime, policy, Memory/VDB, MCP, connectors, Code Prism, or agent surfaces.
Confirm the agent comes from AgentIQ Identity, connectors come from Gateway, and MCP registration is a Gateway projection.
Use the product-specific docs only after the initial shape is working.

Use Gateway registry to inspect provider, end-to-end encrypted, plain, confidential, local, and FHE lanes.
Run the hosted SDK smoke through /mapi first.
Use direct runtime health only as an internal operations proof path.