### Query documentation via HTTP GET

Source: https://support.vlex.com/llms.txt

Perform a search by providing a specific question and an optional end goal as query parameters.

```http
GET https://support.vlex.com/master.md?ask=<question>&goal=<end_goal>
```

--------------------------------

### GET /master.md

Source: https://support.vlex.com/llms.txt

Performs a natural language query against the documentation index to retrieve an answer and relevant sources.

```APIDOC
## GET /master.md

### Description
Perform a query against the documentation index to receive a direct answer and relevant excerpts.

### Method
GET

### Endpoint
https://support.vlex.com/master.md

### Parameters
#### Query Parameters
- **ask** (string) - Required - The immediate question to ask.
- **goal** (string) - Optional - The broader end goal to help tailor the response.
```

--------------------------------

### GET /vincent-by-vlex/vincent/contribute-to-the-knowledge-base.md

Source: https://support.vlex.com/pt-br-vlex-library-knowledge-base

Performs a natural language query against the documentation index to retrieve answers and relevant sources.

```APIDOC
## GET /vincent-by-vlex/vincent/contribute-to-the-knowledge-base.md

### Description
Perform an HTTP GET request on the documentation index to ask a specific question and optionally provide an end goal to tailor the response.

### Method
GET

### Endpoint
https://support.vlex.com/vincent-by-vlex/vincent/contribute-to-the-knowledge-base.md

### Parameters
#### Query Parameters
- **ask** (string) - Required - The immediate question to ask, written in natural language.
- **goal** (string) - Optional - Describes the broader end goal to help tailor the answer.

### Request Example
GET https://support.vlex.com/vincent-by-vlex/vincent/contribute-to-the-knowledge-base.md?ask=How+do+I+contribute?&goal=improve+documentation

### Response
#### Success Response (200)
- **answer** (string) - A direct answer to the question.
- **excerpts** (array) - Relevant excerpts from the documentation.
- **sources** (array) - Sources used to generate the answer.
```

--------------------------------

### Report Generation Prompt Configuration

Source: https://support.vlex.com/vincent-by-vlex-1/vincent-studio/vincent-studio-workflow-examples/building-a-due-diligence-report-workflow.md

Use this prompt structure within a 'Prompt with Context' step to generate a structured due diligence report using the provided template and user variables.

```text
Generate the Report based on the “Due Diligence Report Template” for Business Acquisition, adapting it to the contingencies uploaded by the user. The draft must include:

Cover Page and Introduction
- Explain the context of the transaction.
- Include the name of {target_company}, {buyer_company}, dates, and scope.
- Briefly describe the areas analyzed.

Executive Summary of Critical Contingencies (Red Flags)
- Present the highest-impact contingencies identified.
- Prioritize by impact and probability.
- Use a summary table with columns:
Area | Contingency | Impact | Probability | Recommendation

Detailed Analysis by Area
For each analyzed area:
- Include a descriptive summary.
- Add a complete table listing all contingencies sorted by impact.
- Structure:
# | Contingency | Impact | Probability | Recommendation

Conclusions and Strategic Recommendations
- Summarize the most relevant contingencies.
- Recommend actions regarding:
 – Price negotiation
 – Warranty clauses
 – Mitigation plans
- Include a final conclusion on the viability of the transaction.

Maintain consistency and professional tone
- Use clear, precise, technical language.
- Maintain a corporate, neutral tone.
- Do not invent information — use only the contingencies provided by the user.
- If data is missing, use clear placeholders: [Data not provided].
```

--------------------------------

### Chronology of Facts Extraction Logic

Source: https://support.vlex.com/vincent-by-vlex-1/vincent-studio/vincent-studio-workflow-examples/creating-a-tax-inspection-analysis-workflow.md

Instructions for the AI to extract and format explicit facts from tax documents into a chronological table.

```text
Extract only the explicit facts from the documents, including procedural facts where applicable. Return them in a table with the following columns:
- Date (DD-MM-YYYY)
- Fact
- Source (document name or page number)

Rules:
- Sort the table in ascending order by date.
- If there are multiple documents, combine all facts and remove duplicates.
- If a fact does not include a date, leave that cell empty (do NOT infer dates).
- Exclude opinions, inferences, and questions: only explicit facts.
```

=== COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.