> For the complete documentation index, see [llms.txt](https://isbm.savimbo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://isbm.savimbo.com/overall-description/limitations.md).

# Limitations

Limitations of the indicator species biodiversity methodology

This methodology does not seek to fully quantify biodiversity in its crediting area. Instead, it seeks to provide a fair, transparent, and usable proxy metric for the conservation of ecological zones which are known to be high-value targets for planetary health. 

While this methodology can show the extension of conserved ecosystem as rare and endangered species extend their habitats, and activity, it should not be used to show gains in ecosystem integrity (degraded ecosystem improvements). Which will fall under other methodologies that ideally can interoperate with our [Unit](/calculation/unit-calculations.md).

This methodology is not designed for use for a particular species. Instead, it is encouraged for projects to collect data from as many qualifying species as possible to demonstrate an intact ecosystem in many taxonomic kingdoms. 

As a standalone metric for conserved biodiversity, this methodology is designed to stack or bundle with other important ecological assets. Including soil, air, water, carbon, and equity. However, while it is possible for the presence of biodiversity to infer the presence of intact soil, water, and carbon flows, this methodology should not be used to quantify such inferences which would require specific ecological metrics that fall outside its bounds.<br>


---

# 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://isbm.savimbo.com/overall-description/limitations.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.