# Third-Party Integrations

<details>

<summary><strong>What wallets are supported with Cogitus-powered L1 chains?</strong></summary>

Cogitus supports wallets including MetaMask, Ledger, WalletConnect, and other EVM-
compatible wallets.

</details>

<details>

<summary><strong>Can I integrate Chainlink, Covalent, The Graph, oracles, and bridges?</strong></summary>

Yes, Cogitus supports integration with Chainlink, Covalent, The Graph, LayerZero, and
\
other infrastructure components.&#x20;

Do check our list of supported integrations on the website
&#x20;and the dashboard. We can also support any integration that is not listed there.

</details>

<details>

<summary><strong>Can I deploy smart contracts written in Solidity or Vyper?</strong></summary>

Yes, you can deploy smart contracts using Solidity or Vyper, which are fully compatible
&#x20;with Cogitus-powered Avalanche L1 chains.

</details>

<details>

<summary><strong>How do I integrate third-party explorers or indexers with my chain?</strong></summary>

You can integrate custom explorers or use hosted options like Blockscout and deploy
\
indexers with Traceye. Each Avalanche L1 chain comes with bundled Tracehawk Block
\
Explorer subscription.

</details>

<details>

<summary><strong>Does Cogitus support integration with custom frontends and SDKs?</strong></summary>

Yes, Cogitus provides SDKs and APIs to help connect any custom frontend or tooling to
&#x20;your Avalanche L1 chain.

</details>


---

# 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.cogitus.io/faqs/third-party-integrations.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.