AgentShip Embed Door — Ship a Governed Agent in Your Product
Full Embed door walkthrough: /ship checklist, publish tokens, iframe, knowledge, brand, usage — same FuseIQ engine as Console.
Walkthrough checklist
Intermediate- 1Create agent on /ship/agent, attach knowledge
- 2Connect token + brand, then open iframe embed
- 3Send a test message and confirm Usage
- 4Optional: Guide (last in nav) or Desktop A–Z PDF
Success criteria
Governed agent in your product iframe — same FuseIQ engine as Console
Embed is FuseIQ's Embed — ship in your product — not a separate product.Same governed agent runtime inside your product: iframe/widget, publish tokens, metering and audit — client-facing, not a second product. Console remains the control plane for agents, keys, and spend. Operators keep Console for Swarm, Eval, and fleet control.
Two doors, one engine
- Console — Operator door into FuseIQ Work OS: Instant proof & field jobs, multi-agent Swarm and FuseMind as advanced modes (not separate products), HITL Approvals, Eval, Knowledge Vault, Agent Wallet/BYOK, Live connectors + Agent tools, SSO (Pro+), Runs with proof.
- Embed (AgentShip) — light builder at /ship, public marketing at /agentship, customer iframe at /embed/{agentId}
- One FuseIQ engine — shared auth, audit, metering, agents, Agent tools (MCP), and proof
AgentShip chrome
Light embed-door presentation under data-agentship-theme. Console keeps dark ops chrome. Full market LLM catalog is in Console Settings — AgentShip uses simple model presets only.
A–Z walkthrough
Desktop PDF is the primary guide. In-app Guide is last in the nav:
Builder checklist (/ship)
What customers see
- Token-scoped shell: /embed/{agentId}?token=…
- Run API through the same governed agent runtime as Console
- No FuseIQ dashboard session required for end users