> For the complete documentation index, see [llms.txt](https://agnostico.gitbook.io/agnostico/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://agnostico.gitbook.io/agnostico/introduction/mission.md).

# Mission

We at Deltastack, having identified some of these issues and in the quest to find a lasting solution to them decided to build Agnostico to

1. be the bridge between those who are creating value, and those who need Web3 value.
2. give real ownership to the developers who create value on the blockchain and even a means to earn from their codes.
3. create a means for business owners, entrepreneurs and citizen developers with no prior knowledge of smart contracts to integrate web3 into their businesses with just a few clicks.

The Agnostico initiative gives open-source smart contract developers a choice to publicize their codes on the platform to make reusing them by others as easy as deploying a contract without writing a single line of code.

EVM-compatible blockchains have contributed to the growth of cryptocurrency adoption recently. Developers now implement various standards customized to suit their purpose when creating dApps for their projects, as we see in the surge of the DeFi dApps from 2020 and lately, tokens with reflections.

Since all the information on the public blockchains is by definition, public, the space thrives with open-source initiatives, so it is possible to find the source code of smart contracts on explorers such as etherscan, bscscan and snowtrace  to name a few and then implement them in your own dApp.

### Guides: Jump right in

A deep dive into the Agnostico Protocol:

{% content-ref url="/pages/hWm7MjRYt1qJN01pmY1y" %}
[Sharing Your Code On Agnostico](/agnostico/how-it-works/sharing-your-code-on-agnostico.md)
{% endcontent-ref %}

{% content-ref url="/pages/uAfl7uyUesD1zd3L3fZr" %}
[Deploying Code From Agnostico](/agnostico/how-it-works/deploying-code-from-agnostico.md)
{% endcontent-ref %}

{% content-ref url="/pages/CVJxCTosYxtV1kb25Oee" %}
[Terms And Conditions](/agnostico/compliance/terms-and-conditions.md)
{% endcontent-ref %}

{% content-ref url="/pages/a6bdhXzEnsYWxXHuhZVb" %}
[Privacy Policy](/agnostico/compliance/privacy-policy.md)
{% endcontent-ref %}

{% hint style="info" %}
**Good to know:** your product docs aren't just a reference of all your features! use them to encourage folks to perform certain actions and discover the value in your product.
{% endhint %}

### Fundamentals: Dive a little deeper

Learn the fundamentals of MyProduct to get a deeper understanding of our main features:

{% content-ref url="/pages/uJH8dmH62JKCYDlxA0SA" %}
[General](/agnostico/q-and-a/general.md)
{% endcontent-ref %}

{% content-ref url="/pages/w1YIk4dxAmUa88ix8RwP" %}
[Community ](/agnostico/q-and-a/community.md)
{% endcontent-ref %}

{% content-ref url="/pages/caSB2Fbaqq13WWFyiY9b" %}
[Fees And Royalties](/agnostico/q-and-a/fees-and-royalties.md)
{% endcontent-ref %}

{% hint style="info" %}
**Good to know:** Splitting your product into fundamental concepts, objects, or areas can be a great way to let readers deep dive into the concepts that matter most to them. Combine guides with this approach to 'fundamentals' and you're well on your way to great documentation!
{% endhint %}


---

# 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 dynamically by asking a question.

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

```
GET https://agnostico.gitbook.io/agnostico/introduction/mission.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.