The .BOT description is a human-readable open-source model for building a range of conversational AI.
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.

.BOT Description (version 1.1)

What is .BOT

The .BOT description is a human-readable open-source model for building a range of conversational AI.


Part of the SEED token project. This is a sneak preview - there is more to come. See the Wiki for more information.

About the SEED Token Project

SEED democratizes AI by offering an open and independent alternative to the monopolies of a few large corporations that currently control conversational user interfaces (CUIs) and AI technologies. SEED's licensed, monetized open-source platform for bots on blockchain supports collaboration and creative compensation that will exceed the proprietary deployments from industry giants. We are also giving users back control of their personal data. Find out more about the SEED Token project at

How to contribute - how to get involved

Go to our Developers Garden to see all featured projects, pick one and fill out the Developer Interest Form. If you rather like to discuss ideas before rolling up your sleeves, please come visit our Discord channels for developers

.BOT Description

Like .HTML for the web, .BOT it is a simple model that allows inexperienced developers, content authors, and engineers to build and distribute conversational user interfaces completely platform independent. Whether they be chatbots, assistants, conversational avatars for VR or AR or even video bots the .BOT format is intended to work with a range of modalities.

Modalities for a conversation with a bot can be the following:

  • text
  • voice
  • facial expressions and gestures (3D avatars and video)

This simple yet powerful approach is scalable, modular, and integrates with a range of channels and blockchains. It comes after many years' experience developing conversational UI, however it is also the beginning of a dialogue around how to build conversations.

Examples of channels (bold: already available):

  • Web (all modalities)
  • Telegram (text)
  • Facebook (text)
  • Signal (text and video)
  • Skype (text and video avatars)
  • Amazon Echo (voice assistants)
  • Snips (open-source voice assistants)
  • VR (3D avatars)
  • AR (3D avatars)
  • Virtual Worlds (3D avatars)


These files are made available to you on an as-is and restricted basis, and may only be redistributed or sold to any third party as expressly indicated in the Terms of Use for Seed Vault.


To define a complete bot language that gives servers the possibility to build a bot with all its logic, including external services configuration, conversation logic flow, avatar library and any other information needed to create and execute a bot.

The format used to store the .BOT description is JSON, use this link in order to see its schema.


The description file is divided into sections to group the parameters:

  • Basic information: It is defined on the first level of the JSON file and includes the bot ID, name and other basic parameters.

  • Author: It includes as much information the author wants to share about itself. It could go from anonymous bots to pretty detailed author information including address and wallet information.

  • License: On this section is defined the license of the bot.

  • Remuneration: Here is defined the remuneration method selected by the authors in order to collect tokens on bot usage.

  • Tags: To help users to discover the bot into the search engine, the author is able to set different tags to the bot.

  • Modes: Defines the modes available for the bot. Examples: chat, voice, avatar, VR.

  • Channels: Defines the configuration of each channel where users can use the bot.

  • Media: Here is listed all the files used to deploy the bot. It includes the thumbnail and all the files necessary to create a 3D avatar following the ACTR standard.

  • Runtime: This section is filled by the server that is running the bot. Includes information about port, server, etc.

  • Modules: Defines the internal modules used on the bot.

  • Services: Here is defined all the external services used by the bot, including main services like voice recognition, to third party services like mapping or weather information.

  • Connections: Bot to bot conversation configuration.

  • Logging: Includes the information about logging method used by the bot.

  • Conversation Flow: All the conversation logic is contained on this section. For detailed information check the .FLOW documentation.

Check the structure documentation in order to get more detailed information related with the sections.

Runtime information

Even when almost all information is provided by the developer, some information is filled by the server that is running the bot. The runtime section is completed on the deployment process.

    "runtime": {
      "server": "serverID",
      "type": "string",
      "IP": "ip_address",
      "port": "integer",
      "encoding": "string",
      "seedAddress": "string",
      "mode": "string",
      subscribers: "array"

Basic example

With a minimum number of parameters is possible to define a bot into the server:

"bot": {
    "ID": "",
    "name": "Example bot",
    "description": "05f079c46d096717604cc815f8eb5886",
    "version": "1.0",
    "language": "english",

    "remuneration": {
      "method": "free",
    "author": {
      "name": "John Doe",
      "email": "",
      "seedAddress": "17mmd6HfhkFB2kLy2GBbWenn48YJf7mGwg"

    "modes": {
      "chat": true

    "channels": {
      "channel": {
        "name": "web",
        "enabled": true,
        "mode": "chat",

    "media": {
      "thumbnail": "",

    "conversationFlow": {
        "url": ""


Check a more complete example to see the structure of the other sections.

Enhancements on version 1.1

On version 1.1 we improved the description adding:

  • Sentiment Analysis server configuration
  • SMTP server information
  • oAuth configuration
  • Extra runtime variables



Feel free to throw general questions regarding SEED and what to expect in the following months here on GitHub at @consiliera ( ☀️

Connect with us elsewhere

Seed Vault Code (c) Botanic Technologies, Inc. Used under license.