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

# First Analysis

This first guide is going to help you to run your first [Analysis](/docs/development/concepts.md#analysis).

> If you're not familiar with GraphQL, please have a look at its [dedicated section](/docs/graphql/overview.md) in this documentation.

In order to analyse your first content, you'll have to send a request to our API. This request is going to launch the AdSecure's [crawler](/docs/development/concepts.md#crawler) on the content of your choice.

## Prerequisites

Before starting this guide, please be sure that you're ready to use our service by following the steps illustrated in the [Quickstart](/docs/development/quickstart.md) section.

## Simple case

For the purpose of this first example, we're going to analyse a simple web page:

```bash
https://examples.adsecure.com/simple
```

In order to ask the AdSecure's [crawler](/docs/development/concepts.md#crawler) to analyse this content, we need to create a new [`Analysis`](/api/graphql/analysis.md) entry. When you create a new [`Analysis`](/api/graphql/analysis.md), the AdSecure's [crawler](/docs/development/concepts.md#crawler) is informed that a new task needs to be handled and start analysing the provided content.

[The entry's creation in GraphQL](/docs/graphql/forming-calls.md#about-query-and-mutation-operations) is associated to a `mutation` query and because we want to analyse the content of `https://examples.adsecure.com/simple`, we're going to put this URL as the value of the `input.content` parameter.

Also, and in order to be able to retrieve our analysis later in this guide, we're going to ask the GraphQL API to return us the [`Analysis`](/api/graphql/analysis.md)'s `id`.

**Query**

```bash
mutation {
  createAnalysis(input: {
    content: "https://examples.adsecure.com/simple"
  }) {
    id
  }
}
```

**Response**

```json
{
  "data": {
    "createAnalysis": {
      "id": "YW5hbHlzaXN8YThiYzk0M2ItNTY3ZS00NzA5LWIwOWItMTI1YmMzNGMxMjUwfDIwMTgtMDktMDI="
    }
  }
}
```

Congrats! You've just created your first analysis. It was pretty simple but it one of the most important queries that you'll have to make against our API.

From that point, a new [`Analysis`](/api/graphql/analysis.md) entry has been created in our database and the AdSecure crawler is now analysing the `https://examples.adsecure.com/simple` web page.

As the [analysis](/docs/development/concepts.md#analysis) is going to be complete after a few seconds, you can now take a look at the [understanding analysis results guide](/docs/guides/understanding-analysis-results.md), that will come handy in order to know where to look in the response.

## Next steps

These examples were illustrating some simple use cases of our service. As your own usage could require more advanced features, we're inviting you to keep on discovering our API through the others guides available:

* [Select a specific Location](/docs/guides/select-a-specific-location.md).
* [Select a specific Device](/docs/guides/select-a-specific-device.md).
* [Configuring the Notification Service](/docs/guides/notification-service.md).
* [Managing Custom Alert Rules](/docs/guides/custom-alert-rules.md).


---

# 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.adsecure.com/docs/guides/first-analysis.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.