> For the complete documentation index, see [llms.txt](https://docs.taloflow.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.taloflow.ai/getting-started.md).

# Getting Started

Here's how to get a quick start with Taloflow.

## Setup

### Signing up

You can [Sign up](https://use.taloflow.ai/signup) for a Taloflow account using email, or your Google, Microsoft or GitHub account.

### Dashboard

Once in the dashboard, you'll be able to start creating the evaluations mentioned above by clicking the "Create evaluation" button.

### Creating an Evaluation

Once you've clicked "Create new evaluation" from the Dashboard, you'll be asked:

1. to select the Category you want to run an evaluation for; and
2. to combination of use cases you want to use

{% hint style="info" %}
Use cases are fully adjustable, so choose any number that may be relevant from the available list.
{% endhint %}

After a few seconds, you'll have an evaluation ready-made for you to work with.

### Using the Evaluation

The evaluation comes in the form of a collaborative text editor with lots of smart blocks that you can add, toggle, and configure to suit your reporting needs or provide new insights into your decision.

You can go to the Tables view, which allows you to prioritize your requirements, features and weight dimensions manually to your liking, and add or remove products.

{% hint style="info" %}
You can switch back and forth between the Report and Tables view at your leisure.
{% endhint %}


---

# 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.taloflow.ai/getting-started.md?ask=<question>&goal=<user_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.