> For the complete documentation index, see [llms.txt](https://whitepaper.ivault.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.ivault.io/about-ivault.md).

# About ivault

## There are countless companies that talk about cutting overconsumption. We’re one of the few actually doing something about it.

#### ivault puts a planet-friendly lifestyle in the palm of your hand

ivault is a sharing app that registers and verifies items on the blockchain using our patented technology. This means anyone with a smartphone can rent, lend or sell their stuff – securely and with zero risk to privacy.

The potential is enormous. With ivault, borrowing a neighbor’s ebike will be easier, cheaper and faster than buying one new. And the feel-goods are free and endless – from meeting cool new people to just helping each other out (not to mention taking control of your carbon destiny.)


---

# 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://whitepaper.ivault.io/about-ivault.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.