ToT GPT

Vince Andrei Isip

25 Sep 2025 — 2 min read

TOT GPT

Another commands that caters actions that is configurable without doing coding.

Outline

UI
Configuration
REST API

UI

A sidebar contains list of commands available
By default it will always have Knowledge Based, everything else will be retrieve from Configuration Sheet
An action to sidebar when selected will default to corresponding commands it contains, for example Knowledge Based will have kb:answer
Everything else will have mygpt:ask --name action
Inputting in the chatbox will use that corresponding command as base and will connect your input message from it
Custom commands like kb:match, help will work still.
Can Send URL enclosed in quotes, supported links Trello, Freescout

Configuration

Link
By default will have mygpt:ask sheet
It will contains all available MyGPT commands
Can edit, remove or add actions as longs it follows the columns provided
Columns:
1. label - Title that will be shown in the sidebar
2. id - identification, just provide this one
3. description - helptext when hovering the title in sidebar
4. action - the action that will be use by the bot
5. prompt - instruction whenever an input is provided
6. model - model of OPENAI, optional
7. active - TRUE / FALSE , determines wheter to display or not in sidebar
8. system - base prompt or instruction, persona like

REST API

Link
Exposing POST and GET Method to use Mygpt:ask externally via REST
Please the collection for examples

Selecting Krabs and using krabs as command

Input with links with another texts, enclosed to quotes to work

Approach: Improve Bot Discoverability with Search and Team Scoping

1. Global Bot Search Bar What: * Add a persistent search input at the top of the bot directory. * Search should match: * Bot name * Short description * Tags / keywords * Owner or team (optional enhancement) 2. Role-Based Bot Filtering What: * Automatically filter bots based on the user’s authenticated role, team, or department.

Browse & Search Licenses

Overview This deliverable introduces a searchable License List page within OpsConfig. The page allows operators to browse and locate licenses using substring search across key identifiers, while ensuring all sensitive data remains masked according to the ClientConfig API response rules. The feature is read-only and intended to support operational visibility

License Details (View‑Only)

Overview The License Details (View‑Only, Masked) feature provides operations users with a secure, read‑only view of license‑specific client configuration data. Configuration is fetched via the ClientConfig API and rendered exactly as returned, with all sensitive fields masked. No unmasking or editing capabilities are provided. Scope & Goals

How do you setup identity or age verification so that only certain locations need to get verified?

Answer: Use Location-Based Identity Verification. This is enabled via the locationRestrictions.requiresVerification attribute in your application configuration to define which countries and regions require verification. Summary Token of Trust now supports location-based verification requirements through the locationRestrictions configuration. This feature allows you to specify which geographic locations (countries and regions)