> 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/new-mexico/new-mexicos-opioid-settlements.md). # New Mexico’s Opioid Settlements *This Community Guide will describe how New Mexico is spending its opioid settlements, and whether New Mexico is working to ensure community access to opioid settlement funds. Last revised September 1, 2024.*

Total Funds

$869.92 million[1]

[1] Total is rounded. See The Official Opioid Settlement Tracker Tally. Accessed September 1, 2024.

Allocation

55% to local governments and 45% to the state


Mechanism

State-Local Agreement (New Mexico Allocation Agreement and 2023 Addendum); Legislation (N.M. Stat. Ann. Secs. 6-4-28 and 6-4-29)

55% Local Share

45% State Share

Ultimate Decisionmaker(s)Local officials for cities and countiesNew Mexico state legislature
Decision-making ProcessLocalities decide autonomouslyNew Mexico state legislature appropriates monies from the Opioid Crisis Recovery Fund
SupplantationNot prohibitedNot prohibited
Grant FundingUp to each locality (availability and processes will vary)No
Public InputUp to each locality (not required)No opportunities available (not required)
Advisory BodyUp to each locality (not required)No (not required)
ExpendituresNeither public nor intrastate reporting requiredNeither public nor intrastate reporting required
UpdatesTo find updates on the local share, a good starting point is to check the websites for your county commission, city council, or local health department. See also individual localities’ opioid settlement-specific websites, e.g., Bernalillo County and City of Albuquerque (joint partnership) and Las Cruces.A single resource containing state share updates could not be found.
--- # 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/new-mexico/new-mexicos-opioid-settlements.md?ask=&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.