> For the complete documentation index, see [llms.txt](https://services.godini.agency/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://services.godini.agency/how-we-work.md).

# How we work

Managing a project and maintaining interaction with the community in a healthy way that promotes proper engagement is quite challenging.

In the crypto universe security and trust are watchwords and for that we have at least 3 packages to present. To keep the project properly engaged and with low cost.

In the following I intend to show you our way to keep your project walking smoothly

{% hint style="success" %}
**Good to know:** We accept NFTs or Tokens as part of payment. It will generating a genuine interest in the project. And will free the owners of the projects from having large amounts of liquidity.
{% endhint %}

When taking new jobs we require a minimum contractual relationship of 1 month and 50% of basic cost paid in advance. This way we can give our work seriousness, since taking metrics in less than 1 month is very volatile and does not reflect real performance. Added to this, neither party is benefited if they hire an agency and after a week they disengage.


---

# 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://services.godini.agency/how-we-work.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.