> For the complete documentation index, see [llms.txt](https://docs.amesa.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.amesa.com/build-multi-agent-systems/create-a-project.md).
# Create a Use Case
A use case is a collection of agent orchestrations for the same problem. The best way to use AMESA is to build multiple orchestrations within the same use case using different design patterns and variations. This allows you to iterate and improve for the best possible performance.
All orchestrations within a use case share the same simulator and the same overall KPI.
## Create a Use Case in the UI
To create a use case, click on New Use Case in the upper right-hand corner of your dashboard.
You'll be prompted to enter the simulator associated with your use case and then choose your team.
### Set KPI and ROI
After you select your simulator and team, you'll be prompted to set the KPI and ROI for your use case.
The KPI is the top-level goal, the most important metric you are trying to optimize that you will use to evaluate the performance of your team of agents. Choose the sensor variable that represents this metric to serve as your KPI.
For benchmark value, enter the current performance level on the KPI. This is the number that your agents will attempt to outperform. Add the benchmark units where prompted.
The ROI section allows you to represent agent performance in terms of financial impact. Enter the value in dollars of a specific percentage improvement in the KPI (either increase or decrease depending on the problem).
After agents are trained, the platform will use this information to provide data and visualizations about the performance on the KPI compared to the benchmark and about the financial return on investment on the Benchmarks page.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.amesa.com/build-multi-agent-systems/create-a-project.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
