# Vision

GraphLinq is a set of tools, including an IDE and an engine, to automate various processes and tasks. With GraphLinq, users can create automation workflows using simple node-based graphs, without the need for coding skills. The platform supports multiple blockchains and centralized data streams, allowing for seamless integration with existing systems.

The GraphLinq platform is powered by the GLQ (GraphLinq Chain's native cryptoasset) which can be used to run graphs on the mainnet to automate tasks, and to pay gas fees on our chain. Users can easily listen to transactions on popular blockchain networks like Binance Smart Chain and Ethereum, trigger events, and perform conditional regular expressions with just a few nodes.

Today, GraphLinq is making it possible for people and organizations to automate a wide range of workflows and processes with ease. With GraphLinq, users can save time and reduce costs by automating tasks that would otherwise require manual effort. The platform also provides a safe, secure, and accessible place for data to be stored and maintained, which is crucial for keeping services running smoothly.

At its core, GraphLinq's vision is to create a more efficient, cost-effective, and automated future by empowering people to automate their workflows and processes with ease. With its cutting-edge technology and community-driven approach, GraphLinq is positioning itself at the forefront of the decentralized automation revolution.


---

# 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.graphlinq.io/dev-tooling/introduction/vision.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.
