feat: ai hub

Author: aaitor

docs/environments/08-ai-hub.mdx

@@ -0,0 +1,32 @@
+---
+sidebar_position: 8
+description: Nevermined AI Hub
+---
+
+# Nevermined AI Hub
+
+## Introduction
+
+The Nevermined AI Hub (aka AI Hub or Hub) is a set of infrastructure and AI services provided by
+Nevermined with the intention of making simpler the delivery of AI Agents and services for
+developers.
+
+## Benefits 
+
+The AI Hub provides:
+
+* A backend API implementing the
+  [Nevermined Query Protocol](https://docs.nevermined.io/docs/protocol/query-protocol). This backend can provide the REST API for querying any AI Agent. So AI Builders don't need to define and build the API themselves and focus on the AI piece.
+* Access control. Only users that are subscsribers for the Payment Plan giving access to the Agent can send Tasks to it.
+* Dynamic cost of the queries of the users depending on the AI Tasks complexity. The AI Agent can report back the cost in credits of the individual Steps composing the task returning back the **cost** attribute. The total cost of the task can not go over the maximum cost pre-defined in the task.
+* Automatic accounting for the usage of the Agent. Subscribers sending Tasks to the Agent will be charged in credits for their Tasks. When they use all the credits they have available the access will be restricted, so if they want to continue using the Agent they must topup.
+* Orchestration of tasks. The backend allow AI builders to define their workflow of Steps and receive the Steps to process in the right order. When all the Steps resolving a Task are **Completed**, the backend will complete the whole Task successfully. If any of the Steps fails, the backend will complete the whole Task as **Failed**.
+
+## How an AI Builder can use the AI Hub?
+
+It's very simple. An AI Builder just needs to:
+
+1. Get their own [Nevermined API Key](../tutorials/integration/nvm-api-keys)
+2. Install the [Payments library](../libraries/) in their project
+3. Integrate with the AI Hub to start [processing AI Tasks](../libraries/process-tasks)
+

docs/libraries/08-process-tasks.md

@@ -9,7 +9,7 @@ import TabItem from '@theme/TabItem';
 # How AI Builders can process AI Tasks?
 
 :::note
-This feature is specific for AI Agents Services using the Nevermined AI Infrastructure.
+This feature is specific for AI Agents Services using the <ins>Nevermined AI Hub</ins>.
 :::
 
 ## Benefits of delegating the API to Nevermined AI Infrastructure
@@ -63,6 +63,21 @@ The AI Builders can create simple worker AI process subscribing to Nevermined to
   </TabItem>  
 </Tabs>
 
-This means with this feature, creating an AI Agent is as simple as calling a subscribe and resolving the steps part of the tasks.
+Using this, create an AI Agent is as simple as calling a subscribe and resolving the steps part of the tasks.
 
+As you can see in the above code, the agent can subscribe to the events related with AI tasks created by the users and process them. For doing that it just needs to implement a callback function that will get the AI task input parameters and process it.
+
+### AI Tasks and Steps
+
+The AI tasks are composed by several steps. Each step is a part of the task that the AI Agent needs to process. The steps are processed sequentially and the agent can update the status of the step and the output of the step. You can see the steps as a workflow that the AI Agent needs to process to be completed.
+
+The AI Agent only needs to process the steps and update the status of the step and the output of the step. The rest of the logic is managed by **Nevermined AI Hub**.
+
+When a user requests a task to an AI Agent, by default is created one task with one step. This first step has the **"init"** name. When the AI agent receives the **init** step can:
+
+* If the AI task is simple and **doesn't require several steps**, it can process the step and update the status of the step to **Completed** and the **is_last** attribute as **true**. This will mark the whole task as completed.
+
+* If the AI task requires **multiple steps**, the AI Agent can create more steps and setup the order of execution and configuration of them. This can be done by defining the **name**, **order** and **predecessor** step. 
+
+We will see different code examples about how to do this in the following section.