A credential used to authenticate a user or application attempting to access a third-party API (Application Programming Interface) such as OpenAI, Google, Replicate, ElevenLabs, etc. In Omnitool, users are required to provide their own API keys (BYOK) for the API they intend to use. This key is stored locally on the user's system for security purposes and must be entered in the API management section to activate the corresponding blocks.


Previously called "Component". A single unit of functionality within Omnitool. Blocks can perform a variety of actions, requesting an API, manipulating text/image, or outputting the result to file. By connecting blocks together, users can build complex recipes. Each block is designed to be interoperable, ensuring smooth data format transfers and integration.


Previously called "Workflow". A sequence of interconnected blocks in Omnitool that performs multiple API calls or executes scripts in a defined flow. Recipes are created by arranging these blocks in a sequence to fulfill a specific AI use case.


A pre-made recipe created by the Omnitool team or contributors. It serves as a demonstration use case or starting point for users to craft their own recipes.


A plugin extends the functionality of Omnitool's core system. It can add new blocks, tools, or create custom user interfaces. Extensions allow developers to tailor Omnitool to their specific needs and preferences on both the client and server sides, providing a convenient way to prototype AI-powered applications.

Last updated