Smart365Guide ASDK · Agentic SDK

Give agents a supported path through your software.

Connect the knowledge your application already has to the tools an agent can actually use. Publish the path, expose relevant field rules, and keep actions within the host application’s permissions.

Set up ASDK Read discovery manifest

Your application

SDK + reviewed workflows

ASDK connection

Structured guidance + MCP tools

Compatible agent

Browser controls or granted backend actions

Why a website URL is not enough

An ordinary agent may only fetch page text. It might not run JavaScript, share the user’s logged-in browser, or have any browser controls. The widget does not automatically register tools inside Codex. ASDK offers two explicit connection paths.

Browser-capable agents

After licensed SDK initialization, read published paths through the browser API. No custom guide registration is required for recorded, reviewed workflows. The agent uses its existing authorized browser controls to follow the path and checks the real result.

await Smart365Guide.getASDKContext({
  goal: "invite a teammate"
});

MCP-connected agents

Configure the ASDK MCP endpoint with a delegated agent key. The agent can discover its applications and fetch published paths, selectors, input rules and dropdown options. Registered backend capabilities retain their separate grants, approval and verification checks.

https://www.smart365guide.com/api/v1/asdk/mcp

From embed to usable guidance

Register your application and install its browser SDK on the relevant pages.
Have an authorized operator demonstrate the task. Review and publish the resulting workflow. Enable its automation setting only for approved autonomous use.
Enable Agent integration and Guide in the company/application feature package.
Connect the agent through its browser tools or ASDK MCP. Keep delegated keys in the agent runtime.
Test input rules, account permissions, missing access and the saved business result before enabling automation.

<!-- Browser embed: use your application's public SDK license -->
<script src="https://www.smart365guide.com/sdk/smart365guide.js"
  data-license-key="YOUR_APPLICATION_SDK_LICENSE"
  data-endpoint="https://www.smart365guide.com"></script>

<!-- Optional static discovery for readers that do not run JavaScript -->
<link rel="asdk" type="application/json"
  href="https://www.smart365guide.com/.well-known/asdk.json">

The discovery link is public connection metadata. It does not provide tenant data or authorize access. A client must choose to use it and complete the supported connection.

Codex setup

Create a Network agent key in the ASDK portal. Set it as S365_NETWORK_KEY in the environment that launches Codex, then run:

codex mcp add smart365guide-asdk \
  --url "https://www.smart365guide.com/api/v1/asdk/mcp" \
  --bearer-token-env-var S365_NETWORK_KEY

Restart the client and ask it to call asdk_list_applications, then asdk_search_workflows and asdk_get_workflow for your application. Use asdk_get_field_options for additional dropdown options. Guidance reads are bounded, paginated and do not call a model.

Open guided setup and connection test

What ASDK does and what still needs integration

ASDK exposes reviewed knowledge and authorized tools for integrated web applications. It does not turn every URL into an executable app, discover all hidden backend rules, control an agent’s private runtime, or authenticate to customer accounts automatically. Browser paths are guidance, not independently verified backend operations. Custom controls, inaccessible frames and native apps need adapters.

Codex CLI configuration and MCP transport are tested reference paths. Claude, ChatGPT and local models require a client with compatible MCP authentication and tools; support varies by client. This release does not establish new token or latency savings.