SDK
The implemented surfaces are a standalone widget script, a JS API, trigger elements, and internal Rails/Stimulus helpers.
This is the real embedding stack exposed in PrintSpeak today, without overstating it as a React SDK or headless platform.
Feature family placeholder
Reserved for a dedicated interface preview, workflow diagram, or annotated screenshot.
MATRIX
Script-tag embed
Includes
A standalone `printspeak-agent.js` widget loaded with `data-domain` and `data-token`.
Why it matters
This is the primary external integration path documented in the SDK guide and usage UI.
Rails helper components
Includes
`ai_agent`, `ai_input`, `ai_submit`, `ai_message`, and related helper methods for internal app surfaces.
Why it matters
Internal product embedding is helper-driven rather than a separate component SDK package.
Stimulus controller integration
Includes
Role-based agent controllers wired to `AgentsChannel` for streaming and action handling.
Why it matters
The frontend runtime is explicitly built around Stimulus plus ActionCable.
Trigger links and buttons
Includes
Elements with `data-psagent-token` can open different agents with different context on click.
Why it matters
This is a real multi-agent embed pattern, not just a single fixed launcher.
Auto-send messages
Includes
Trigger elements can include `data-psagent-message` to open the chat and send a predefined prompt.
Why it matters
Useful for routing pricing, support, or onboarding flows into purpose-built prompts.
Programmatic widget API
Includes
`PSAgent.open`, `close`, `send`, `destroy`, `showToggle`, and `hideToggle`.
Why it matters
The JS API is real and should be described directly instead of implying a broader event SDK.
Multiple widget instances and roles
Includes
The frontend architecture supports multiple agent interfaces and role-specific controller behavior.
Why it matters
This is visible in the controller docs and makes the embed/runtime story more concrete.
Config precedence
Includes
Widget config resolves from script data attributes and can be overridden with `window.PSAgentConfig`.
Why it matters
This is an actual implementation detail that matters for advanced embeds.
| Capability | Includes | Why it matters |
|---|---|---|
Script-tag embed | A standalone `printspeak-agent.js` widget loaded with `data-domain` and `data-token`. | This is the primary external integration path documented in the SDK guide and usage UI. |
Rails helper components | `ai_agent`, `ai_input`, `ai_submit`, `ai_message`, and related helper methods for internal app surfaces. | Internal product embedding is helper-driven rather than a separate component SDK package. |
Stimulus controller integration | Role-based agent controllers wired to `AgentsChannel` for streaming and action handling. | The frontend runtime is explicitly built around Stimulus plus ActionCable. |
Trigger links and buttons | Elements with `data-psagent-token` can open different agents with different context on click. | This is a real multi-agent embed pattern, not just a single fixed launcher. |
Auto-send messages | Trigger elements can include `data-psagent-message` to open the chat and send a predefined prompt. | Useful for routing pricing, support, or onboarding flows into purpose-built prompts. |
Programmatic widget API | `PSAgent.open`, `close`, `send`, `destroy`, `showToggle`, and `hideToggle`. | The JS API is real and should be described directly instead of implying a broader event SDK. |
Multiple widget instances and roles | The frontend architecture supports multiple agent interfaces and role-specific controller behavior. | This is visible in the controller docs and makes the embed/runtime story more concrete. |
Config precedence | Widget config resolves from script data attributes and can be overridden with `window.PSAgentConfig`. | This is an actual implementation detail that matters for advanced embeds. |
RELATED FAMILIES
ENTERPRISE FEATURES
The real admin surface centers on agent creation, versioning, import/export, scope controls, and operational configuration inside the enterprise UI.
AUTHENTICATION
The implemented access model centers on agent API keys, signed or encrypted tokens, origin controls, and agent/context resolution.
WHITE LABEL
The external widget supports multiple themes, title overrides, display modes, and custom theme builds for branded deployments.