Ecommerce · LumaCart
Products → cart → checkout → verified order.
See the SDK in use
Smart365Guide in ecommerce and healthcare.
Real browser recording with the licensed SDK, synthetic test accounts and a scripted guidance adapter. The narration reuses disclosed AI-generated speech. No external model agent runs and no efficiency benchmark is measured. Login, route permissions and role enforcement belong to the sample application's backend; they are configured separately from the widget embed.
Healthcare · CarePath
Services → appointment → review → verified booking.
Fictional healthcare data. This is a reference app, not a production clinical integration.
Recorded SDK walkthrough · 1 minute 10 seconds
A floating guide. A clear path. Your permissions.
Watch the companion move across a separate sample app, guide a user, fill a real dropdown and provide structured field knowledge. The sample backend checks login and roles: unknown paths return 404, denied actions return 403, and authorized changes are read back.
Real browser recording with the licensed SDK, synthetic test accounts and a scripted guidance adapter. The narration reuses disclosed AI-generated speech. No external model agent runs and no efficiency benchmark is measured. Login, route permissions and role enforcement belong to the sample application's backend; they are configured separately from the widget embed.
A few lines mount the assistant.
<script src="https://www.smart365guide.com/sdk/smart365guide.js"
data-license-key="YOUR_APPLICATION_SDK_LICENSE"
data-endpoint="https://www.smart365guide.com" async></script>Register your application and allowed domain, then use its browser SDK license. Configure appearance and enabled features in the portal. Role integration and executable workflows need host-approved contracts.
Login stays in your application.
People use the software's existing login. Agents should receive owner-approved scoped credentials or a delegated OAuth/session connection. A Smart365 agent key identifies a registered Smart365 account; it does not replace the customer's role checks or make arbitrary username/password login automatic.
A 404 is handled by stopping and returning to an approved path. A 403 requires permission; guidance cannot bypass it.
What the recording shows
- A real floating SDK companion. Drag it beside the work you are doing.
- A few lines mount the guide. Register the app and configure host permissions separately.
- Ask for a goal → follow the approved path → review field choices → save in the host app.
- The adapter receives only the relevant path and live fields. No password is shared.
- Unknown route: 404. Known action without permission: 403. The host checks every request.
- An authorized operator agent can write. The app reads saved state back and records activity.
See the SDK in use
Smart365Guide + your AI agent
Give compatible tool-calling agents structured app knowledge and approved workflows through an MCP or custom adapter. This 1 minute 59 second narrated animated video shows how your app, Smart365Guide, and an agent connect, with smooth AI-generated narration and measured Codex pilot results.
About this video
Animated architecture illustration, with AI-generated voice narration and English captions. It does not connect a live agent or perform a customer action. Codex, Claude, ChatGPT and local model clients require a compatible adapter and validation. The efficiency figures come from the recorded controlled Codex pilot, including SDK startup; other agents need their own measurements. Results vary, and token savings do not guarantee equivalent billed savings.
Video transcript
- 0:00Smart365Guide is the guide layer between your application, your users, and compatible AI agents. Your software provides the knowledge. You keep control.
- 0:12Your team embeds the licensed web SDK and shares relevant page context, fields, and reviewed workflows. Backend permissions remain in your application.
- 0:24Codex, Claude, ChatGPT, and local models can connect through compatible tool-calling adapters. Each client needs configuration and validation before it can act.
- 0:35An agent asks for a goal. Smart365 supplies only relevant context and typed actions, so the agent has a clear, structured starting point.
- 0:46Delegated access, consent, and scopes define what is allowed. Sensitive capabilities can pause for approval. Missing permission stops the gateway request.
- 0:57The gateway follows the published workflow through your REST or MCP provider. It reads back saved state before reporting a verified business result.
- 1:08For people, one chat brings questions, navigation, workflow guidance, and reviewed page commands together. Browser voice is optional, and restart gives a fresh conversation.
- 1:21Product owners can inspect routed actions, approvals, provider calls, verification, and timing. They can revoke delegated access when needed.
- 1:32In our controlled Codex pilot, mean total tokens were 48.4 percent lower, and median completion time was 15.9 percent shorter. Other clients and workflows need their own measurements.
- 1:46Start with your web app and one approved workflow. Visit Smart365Guide dot com to request a free demo. This illustrated video uses AI-generated narration.