# MicroServices

This section shows a list of **microservices** which have already been brought to the Ai-MicroCloud and are ready to be spawned by the user using the steps mentioned in [**Spawn a MicroService Guide**](https://computationaldocs.zeblok.com/zeblok-computational-1/spawn-microservice) under our Quick Start Section of the documentation.

![Fig.1: List of MicroServices ](/files/JRJ8JjVu7JJm9LGvciFN)

**Add MicroService**

![Fig. 2: Add MicroService](/files/b7yrbZNWfn7RC3qnKdD6)

The following are the definitions for the fields shown in the **Create MicroService** form.

**Resource Name** => The name of the WorkStation you would like to give.

**Image Tag** => The Image Name along with tag of the docker container.

**Select Compatible Plan** => This is a multi-select dropdown of the available plans and you have to select the ones suitable for this container.

**Select Default Plan** => This is a dropdown among all the plans chosen in the previous field to choose one of them as the default plan/ recommendation.

**Public Access to MicroService** => Disabling it will only let the superadmin view this container for spawning.

**Description Box** => Provide a suitable description for this WorkStation for the users to understand the capabilities of this microservice.

**Internal Ports** => List of port numbers with their protocol which are required for this microservice to work.

**Upload Image** => Upload an image for this container as a thumbnail.

The below tutorial contains all the detailed steps for onboarding a simple microservice and how to spawned the onboarded microservice into the platform.

{% file src="/files/D2RoVqle3xJTTr2HuUYc" %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://computationaldocs.zeblok.com/info/1.2.6/more/admin-guide/microservices.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.