> For the complete documentation index, see [llms.txt](https://www.opioidsettlementguides.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.opioidsettlementguides.com/minnesota/additional-resources.md).

# Additional Resources

## **Association of Minnesota Counties**

* [Opioid Settlement Resources & Information](https://www.mncounties.org/meetings_and_education/opioid_settlement_resources_and_information.php#revize_document_center_rz621)
  * [FAQs](https://cms1files.revize.com/assocofminnesotacos/document_center/AMC%20and%20Affiliate%20Opioid%20Settlement%20FAQ%20_%20summer2022_final.pdf)

***

## **League of Minnesota Cities**

* [Opioid Epidemic Information and Resources](https://www.lmc.org/resources/opioid-epidemic/)

***

## **Minnesota Department of Human Services**

* [Opioid Epidemic Response Advisory Council](https://mn.gov/dhs/opioids/oer-advisory-council.jsp)
  * Grant Award Update & Evidence-Based Analysis of Opioid Legislative Appropriations ([August 2023](https://edocs.dhs.state.mn.us/lfserver/Public/DHS-8076B-ENG), [February 2022](https://edocs.dhs.state.mn.us/lfserver/Public/DHS-8240A-ENG))

***

## **Minnesota Department of Health**

* [Local Public Health Guide to Spending Opioid Settlement Funds](https://www.health.mn.gov/communities/opioids/settlefunds.html)
* [Drug Overdose Dashboard](http://health.state.mn.us/communities/opioids/opioid-dashboard/index.html)

***

## **Minnesota Management and Budget**

* [Opioid Epidemic Response Spending Dashboard](https://mn.gov/mmb/impact-evaluation/projects/opioid-epidemic-response/spending-dashboard/)

***

## **Minnesota Attorney General’s Office**

* [Fighting the Opioid Epidemic in Minnesota](https://www.ag.state.mn.us/opioids/)
* [Opioid Settlement Payment Amounts](https://www.ag.state.mn.us/opioids/SettlementAllocation.asp)


---

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.opioidsettlementguides.com/minnesota/additional-resources.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
