> For the complete documentation index, see [llms.txt](https://docs.gov.tools/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gov.tools/participate-in-development/govtool-apis/proposal-pillar-api.md). # Proposal Pillar API GovTool's backend services are primarily focussed on reading governance data from Cardano, and showing this to users. Although the APIs for these services are open with a general policy builders are not encouraged to use these, as these are specialised for GovTool and maybe changed without notice. GovTool's Proposal Discussion Pillar is an off-chain forum, to discuss and propose ideas that may become governance actions. This off-chain data is generated by GovTool and cannot be queried by chain indexing. This is why Intersect/GovTool commits to allowing builders/tooling providers to use the Proposal Pillar API. ### Data Access and Use Policy TBD --- # 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.gov.tools/participate-in-development/govtool-apis/proposal-pillar-api.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.