# Key Concepts

## Overview

These concepts are functionalities that persist throughout Squid's Widget, API, and SDK that enable a seamless cross-chain experience for both users and developer. Please read through each feature to understand how they are implemented across Squid

## Squid Functionality

The functionality of the Squid boils down to **3 main functionalities**:

1. [**Route Requests**](/old-v2-documentation-deprecated/key-concepts/get-a-route.md)**(Fetching a Route):** Calculating the most optimized path from one asset to another.
2. [**Route Execution**](/old-v2-documentation-deprecated/key-concepts/execute-the-route.md)**:** The submission and execution of that path on chain.
3. [**Transaction Status**](/old-v2-documentation-deprecated/key-concepts/track-status.md)**:** The validation that the transaction has been completed.

There are **3 advanced functionalities** enhance Squid's API capabilities:

1. [**Transaction Hooks**](https://docs.squidrouter.com/) **(Pre/Post):** Allow transactions to be prepended(prehook) or appended(posthook) to asset transfers for a user. Think unstaking then transferring an asset or transfering an asset across chain then staking.
2. [**Boost:** ](/old-v2-documentation-deprecated/key-concepts/boost.md)Squids novel boost functionality allows cross-chain transactions to be settled in less than 20seconds by using an intent-model, a smart contract overlay which allows a provider to optimistically fulfill a transaction.
3. [**Collecting Fees**](/old-v2-documentation-deprecated/key-concepts/collect-fees-1.md)**:** Always integrators to collect fees associated with transactions. Note, this function is currently not available for v2 yet.

#### **A Note On Up-Time**

Squid aims for 100% up-time with multiple guardrails in place to prevent unintended downtime. If you believe Squid may be experiencing downtime you can check our [status page ](https://status.v2.api.squidrouter.com)to see if there are any outages.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.squidrouter.com/api-and-sdk-integration/key-concepts.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.