RichScripts
DEVELOPER PREVIEW · VERSION 0.4

Add an action assistant
to your web app.

RichScripts AI Action SDK is a JavaScript toolkit for developers. It adds a chat-style control panel to your software so users can find records, open screens, or request an approved change by typing a short instruction.

For example: a user types “Show open requests”, and your application displays the matching requests. Your code defines the actions the assistant can perform.

Try the interactive demo → Get the SDK
Vanilla JavaScriptReact + ASP.NET examplesYour app · Your permissions
SDK demo showing three open customer requests next to the assistant's search response
Actual SDK demo · Fictional customer data · Click to enlarge

What is AI Action SDK?

An SDK is a software development kit: code you add to an application you are building. This SDK provides the assistant interface, an action registry, argument checks, and confirmation cards. You connect those actions to the features and APIs your application already has.

Who is it for?

Developers building SaaS dashboards, customer portals, admin panels, and internal tools.

What do users get?

A simple way to search or navigate by typing requests, with a review step before changes.

How does it work?

Your resolver maps a request to a registered action. Your application checks access and runs that action.

Where does AI fit?

Start with local commands, or connect a model through your own server for flexible language understanding.

What you can try today: this page uses fixed commands and fictional records. The ZChat and MyLiveChat integrations support real read actions or dashboard navigation. Model inference and production write actions require additional application integration.

From request to result.

Explore the three steps, then try them in the working demo below.

01 · Find what matters: A short command filters the inbox and displays matching requests.

01 · Find what matters

A short command filters the inbox and displays matching requests.

Actual SDK screenshots · Fictional records · Local scripted demo · Click a screenshot to enlarge

Try these steps yourself →

Try it on a tiny support inbox.

Watch the application change as you talk to the assistant.

Local scripted demo · No AI API calls
Sample data only · Resets when you reload

Maple Support

Fictional customer requests · Changes stay in this tab

Showing all requests

Draft notes

No notes yet.

Action activity

Ready.

Try the examples above. This preview recognizes a limited set of English commands; it is not a connected language model.

See what the assistant is allowed to do.

Find requests

Filter all, open or closed requests.

Read only · Immediate
Find a customer

Search the sample inbox by name.

Read only · Immediate
Close a request

Review the numbered request before changing it.

Write · Confirmation required
Draft a note

Save a customer note in this tab.

Write · Confirmation required

The application defines this action catalog. Requests to run arbitrary code or unregistered actions are rejected by the SDK.

Small component. Explicit actions.

Full integration walkthrough · ZChat & MyLiveChat →

Mount the SDK inside your application and register the operations users can request. A resolver returns an action name and validated arguments. Read actions run immediately; changes display a confirmation card.

  1. Load the JavaScript file and provide a mount element.
  2. Register your action schemas and execution callbacks.
  3. Connect a same-origin resolver endpoint or a custom resolver.
  4. Enforce authentication, permissions and validation on your server.
<div id="assistant"></div>
<script src="richscripts-actions.js"></script>
RichScriptsActions.mount({
  target: '#assistant',
  endpoint: '/ActionResolver.ashx',
  csrfToken: () => app.csrfToken,
  actions: [{
    name: 'find_requests',
    readOnly: true,
    parameters: {
      type: 'object',
      properties: {status: {
        type: 'string',
        enum: ['all', 'open', 'closed']
      }},
      required: ['status']
    },
    execute: args => app.findRequests(args)
  }]
});

Developer preview: includes the browser SDK, fictional-data demo, ASP.NET server samples, and ZChat/MyLiveChat integration examples. There is no bundled hosted AI service. Your application supplies authentication, authorized operations, and any model inference costs.

Connect the complete sample workflow.

The starter ZIP now includes an authenticated ASP.NET page, model resolver, proposal executor and session data store. Configure your own model key to try real language-to-action requests on fictional records.

  1. Install server-sample/ inside your existing signed-in ASP.NET application.
  2. Merge the example model settings into your protected configuration.
  3. Open ConnectedDemo.aspx after signing in.
  4. Ask for a change, review it, and confirm. The server consumes the stored proposal and updates only the sample session.

These server examples are downloadable source, not active RichScripts customer endpoints. Model calls incur your provider costs. The public demo above remains local and free of API calls.

Build an assistant that can do useful work.

RichScripts AI Action SDK is a developer component for adding a conversational interface to a web application. Instead of treating every request as an open-ended chat, the application defines a small catalog of actions with named parameters. These actions can search records, change the visible view, prepare a note or request an update to an existing item. The assistant helps users reach the features that already exist in your product.

The preview on this page runs entirely in the browser using fictional support requests and a scripted resolver. It demonstrates the interaction without sending messages to a language model. Reloading the page restores the sample inbox. An integration can keep explicit local commands or supply a server-side resolver backed by the model or local inference service chosen by the developer. The browser communicates with your application endpoint; model credentials remain on the server.

Action schemas describe allowed argument types and values. The prototype validates flat string, integer and boolean fields, rejects unknown fields, and checks required arguments. It does not implement the complete JSON Schema standard. Your backend must repeat validation and use the authenticated user's identity to select records and check permissions. Browser-side checks improve interaction but cannot authorize a database change.

Read-only actions can execute immediately. Actions that modify state show the proposed arguments and ask the user to confirm or cancel. A production executor should bind this approval to the proposed action, enforce it on the server and use idempotency keys for retries. The connected sample binds proposals to the signed-in user, keeps separate pending operations across tabs, supports server cancellation, checks their five-minute expiry and returns cached results for duplicate execution requests. Its session data is fictional; real applications still need database transactions, tenant authorization and durable idempotency. The SDK reports action activity through callbacks so developers can connect their own audit trail.

The initial release uses vanilla JavaScript and an isolated component style, with no framework dependency. It includes a model resolver, a sample executor and a connected ASP.NET page, with fictional session data for installation inside an authenticated application. This is a developer preview intended for evaluation and integration experiments. Pricing and a production support policy will be published after the component has been tested against real application workflows.

Can I use it without being a developer?

You can try the demo here, but installing the SDK in your own product requires development work. It is a toolkit for building an assistant inside existing software.

Does it include an AI model or API subscription?

No. Local command mode needs no model calls. If you connect a model, you supply the provider or local service, credentials, billing and usage limits on your server.

Is the demo using real AI?

No. It uses a limited scripted resolver so you can test the workflow without API costs. Your production server supplies model inference.

Can the assistant call arbitrary application code?

The SDK dispatches registered action names only. Your server must separately authorize every action and validate its arguments.

Does it work with ASP.NET?

The JavaScript component is framework independent. The downloadable classic ASP.NET handler demonstrates the resolver contract; authentication and execution remain application responsibilities.

SDK demo screenshot · Fictional data

Open full-size image in a new tab