> For the complete documentation index, see [llms.txt](https://docs.permission.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.permission.ai/getting-started.md). # Getting Started 👋 Welcome to Permission Docs Welcome to the official documentation hub for **Permission**. Permission is a platform built for a future where **AI works for people,** enabling individuals and families to retain agency, clarity, and control as AI systems become more embedded in everyday life. This documentation provides an overview of Permission’s platform, principles, and direction. Inside these docs, you’ll find: * What Permission is and the problem it’s designed to solve * Our vision for the agentic web and A2A economy * Families as a first-class use case for Permission * ASK token utility and roadmap * How the ASK token powers rewards and agent-to-agent value exchange * Resources, FAQs, and smart contract details ### Who This Is For These docs are intended for: * **Individuals** thinking seriously about the future of AI and personal agency * **Families** navigating technology together with intention * **Builders and researchers** exploring agent-based systems and the emerging agentic web * **Developers and partners** interested in building on the **Permission Protocol** — an open-source foundation for permission-based interactions powered by ASK > 👉 Start with What is Permission or explore ASK Token Utility --- # 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 dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.permission.ai/getting-started.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 `build a script that syncs our docs to a CMS` 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.