🚀 Getting Started
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
Updated July 20, 2026
12 min read
Embed is FuseIQ's Embed door — not a separate product.Plain-English input to a governed, cost-tracked agent you embed in your product — same engine, same proof. Operators keep Console for Swarm, Eval, and fleet control.
Two doors, one engine
- Console — Swarm, Eval, governance, SSO, and full operator control for teams shipping production agents.
- Embed (AgentShip) — light builder at /ship, public marketing at /agentship, customer iframe at /embed/{agentId}
- One FuseIQ engine — shared auth, audit, metering, and agents
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:
1
Open /ship/guide (last nav item: Guide).
2
Follow letters A–Z (Arrive → Zero-to-production).
3
Use in-page links to jump to Agent, Knowledge, Connect, Brand, Usage.
Builder checklist (/ship)
1
Create your agent — name, system instructions, simple model preset.
2
Attach knowledge — ground the agent in product docs (Vault-backed when available).
3
Connect embed — publish token, iframe snippet, REST notes, honest MCP labeling.
4
Brand — logo and colors for the embed surface (AgentShip chrome, not Console).
5
Usage — metered embed runs and cost.
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
⚠️
Tokens must validate and include the run scope. MCP claims stay honest — client capabilities only where shipped; do not market unbuilt MCP host features.
💡
Deep book: see repo marketing/books/agentship-embed-door-book.html and docs/guides/agentship-embed-door.md.
Was this helpful?