It also tries to be fast because it is built on top of PPI. The following is a brief overview of what the library does. It generates a unique ID for each request/response cycle; It generates the bot token from these IDs, to uniquely identify the request/response cycle. It then encrypts this, and saves it in the request header, so that the other end can't change it; It provides a way to read the previous and next message IDs from the received stream, so that you can identify a chain of messages; It provides a mechanism for checking the validity of the token. Token validations are performed in each of the modules, the token.validate() method. If your token is expired or incorrect, then an AuthenticationError will be thrown. Some useful examples: coast server = new Server (p, “localhost”, 10243); coast bot = new Bot (server, {Anika : “123”, p : 123, }, {auth : {requested : “123”, previous : “0”, next : “00”, },}); console. Log (bot. Handle (null)); // handles message {1: Hello, world} bot. Handle (null, {message : “Ai! EU OK ICH have”}); // handles message {1: hi} bot. Handle (null, {message : “Sum Tale DES Levels.” }); // handles message {1: hi} The following is the API documentation for the library. An API is a small piece of software that allows users to communicate with your app. A bot can be thought of as part of an application. Here are some ways to interact with the library: The chat API is the primary way to interact with the library. It is built and managed by Small. For use cases requiring more information on the Chat API itself, you may want to look at the discord.chat.java class, which extends Server to include a ChatController. Here are some ways to get the server: The server returns a Server instance. You can make a request to the server with the PPI token in the header: “Anika”, “Pizza”, “123”, or your own request token value. You can obtain the previous and next message IDs from the received stream: “message-id”.