> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sreagent.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Quickstart

> Go from sign-up to your first AI investigation in about fifteen minutes.

export const Plan = ({tier}) => <Badge color="blue">{tier} plan</Badge>;

By the end of this page you will have an account, a Grafana webhook sending alerts in, a data source the agent can query, and a finished investigation of a test alert.

<Plan tier="Free" />

Everything here works on the Free plan. You need to be an organization administrator, which you are automatically for an organization you create by signing up.

<Steps>
  <Step title="Sign up and confirm your email">
    Open the sign-up page and either use a social sign-in button or fill in **Name**, **Organization**, **Email** and **Password** (at least 12 characters), then select **Create account**.

    Signing up creates a new organization with you as its administrator. If your email domain already belongs to an organization, sign-up sends that organization's administrators a request to admit you instead.

    Open the confirmation email and follow the link. Investigations stay disabled until your address is confirmed.
  </Step>

  <Step title="Connect an alert source">
    In the sidebar, select **Integrations**. The **Webhooks** tab is open by default and shows a card for each supported source. Under **Grafana**, copy the **Endpoint URL**. It has this shape, with your organization's own token at the end:

    ```text theme={null}
    https://sreagent.app/webhooks/grafana/<token>
    ```

    Treat the URL as a credential: anyone who has it can post alerts into your organization.

    Then, in Grafana:

    1. Go to **Alerting**, then **Contact points**, and select **Add contact point**.
    2. Choose **Webhook** as the integration type.
    3. Paste the endpoint URL into the **URL** field and set the HTTP method to **POST**.
    4. Save, then assign the contact point to a notification policy so your alert rules use it.

    Grafana's `severity` label sets the severity in SRE Agent: `critical`, `high`, `warning` and `info` map directly, and an alert with no severity label becomes `medium`.
  </Step>

  <Step title="Connect an AI provider (optional)">
    SRE Agent provides shared AI by default, so investigations work without this step. To use your own
    provider, go to **Settings**, then **AI Providers**, then **Add Provider**. After you save it,
    press **Test** on the provider card to check the key. [Connect your
    data](/guides/get-started/connect-your-data) covers it, including how to keep your data on your
    own providers only.
  </Step>

  <Step title="Add a data source">
    The agent can only investigate with what it can read. Still in **Settings**, open the **Data Sources** tab and select **Add Data Source**. Enter a **Name**, choose the **Type** (for example **Prometheus**), enter the **URL**, and set **Authentication** if the endpoint needs it. Select **Test Connection**, and when it reports `Connection successful!`, select **Save Data Source**.

    The Free plan includes one data source. [Connect your data](/guides/get-started/connect-your-data) lists every type, what each one enables, and how to connect AWS with a read-only role.
  </Step>

  <Step title="Send a test alert">
    For a first smoke test you can skip the previous two steps and send the alert right after the webhook step. The investigation then says it had little data to work with. Send a firing alert in Grafana's format straight to your webhook. Replace `<token>` with the token from your endpoint URL:

    ```bash theme={null}
    curl -X POST "https://sreagent.app/webhooks/grafana/<token>" \
      -H "Content-Type: application/json" \
      -d '{
        "alerts": [
          {
            "status": "firing",
            "labels": {
              "alertname": "HighErrorRate",
              "severity": "critical",
              "service": "api-gateway"
            },
            "annotations": {
              "summary": "Error rate above 5%",
              "description": "The API gateway error rate has exceeded 5% for the last 5 minutes."
            },
            "fingerprint": "quickstart-test-1"
          }
        ]
      }'
    ```

    A successful call answers `{"status":"ok","processed":1,"total":1}`.

    <Tip>
      Send a different `fingerprint` for each test. A repeat of the same fingerprint counts as the same alert firing again, not a new one.
    </Tip>
  </Step>

  <Step title="Open your first investigation">
    In the sidebar, select **Alerts**. The test alert appears under **Active Alerts**. Investigations start automatically when an alert fires, so select **Investigations** in the sidebar and open the entry named after your alert. A status of **Pending** or **Running** changes to **Completed** when the agent finishes.

    If no investigation exists for the alert, open the alert from the **Alerts** list and select **Start Investigation**. You can tick **Deep investigation** first to run extra checks on metrics, logs, changes and traces in parallel, which uses more AI tokens.
  </Step>
</Steps>

## What you see

The **Investigation Details** page shows a **Summary**, the **Root Cause**, **Recommendations**, the **Findings** with their evidence, and an **Investigation Timeline** listing every query the agent ran. The buttons at the top let you **Stop** a running investigation, **Retry** or **Expand** a finished one, and generate a **Report** (technical, management or customer).

A test alert about a service that does not exist in your data will produce a thin result. The agent can only report what your data source returns, so point a real alert rule at the webhook to see a full investigation.

<Note>
  The dashboard shows a **Finish setting up** card until everything is connected. It lists the next
  connections to make, including Slack and the GitHub App, and what each one adds. The Free plan
  includes 10 AI investigations and 100 alerts per month.
</Note>

## If something does not show up

| Symptom | What to check |
| - | - |
| The call answers `Invalid webhook token` | The token in the URL must match the one on **Integrations**. After you rotate the token, the old URL keeps working for a limited time and then stops. |
| The alert appears but no investigation starts | Confirm your email address, and check whether an existing investigation already covers the alert. Repeats of the same alert attach to one investigation. |
| The investigation warns that no data sources are connected | Add one on the **Data Sources** tab. Without data to query, results are shallow. |
| **Test** on a provider reports a failure | Check the API key and model name, then test again. |

## Related

* [Run and read an investigation](/guides/respond/investigations): how to read the result of an investigation.
* [Work incidents from Slack](/guides/respond/slack): get alerts and results in a Slack channel.
* [Set up on-call](/guides/respond/on-call): page the right person when an alert needs a human.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.