> For the complete documentation index, see [llms.txt](https://docs.basin.global/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.basin.global/realvalue/why-put-a-value-on-nature.md).

# Why put a Value on Nature?

The [Appendix](/appendix/glossary.md) references thousands of sources as to why and how to value nature. &#x20;

These two quotes ground us in the ***why***:

> "***Only when the last tree has been cut down, the last fish been caught, and the last stream poisoned, will we realize we cannot eat money.***"
>
> \- Osage saying, circa 1893

> "***…by bringing economics and ecology together, we can help save the natural world at what may be the last minute – and in doing so, save ourselves.***"
>
> \- Sir David Attenborough  \
> The Dasgupta Review: the Economics of Biodiversity 2021

The RealValue of Natural Capital expresses the value nature in a language everyone understands: dollars.

***

{% hint style="success" %}
"*BASIN is not financializing nature, we are naturalizing finance.*" - Jeff Stephens
{% 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 by asking a question.

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

```
GET https://docs.basin.global/realvalue/why-put-a-value-on-nature.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.
