> For the complete documentation index, see [llms.txt](https://docs.nearby.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nearby.finance/overview/nearby.md). # Nearby Privacy-preserving infrastructure for real-world coordination across location verification, local communication and offline value transfer. **Nearby Protocol** is a privacy-preserving coordination infrastructure that combines zero-knowledge geolocation, mesh networking and offline payments into a unified ecosystem. Built on Base, Nearby enables users to verify location without exposing sensitive data, communicate without relying on centralized infrastructure and exchange value even when internet connectivity is unavailable. **The protocol is composed of three interconnected layers:** • **Proof of Location:** Private and verifiable geolocation powered by zero-knowledge proofs. • **Nearby Mesh:** Location-aware, anonymous communication through decentralized mesh networks. • **OfflinePay:** Peer-to-peer stablecoin payments that continue to function in disconnected environments. Together, these layers create a resilient foundation for coordination, communication and commerce in both connected and disconnected environments. --- # 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.nearby.finance/overview/nearby.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.