> For the complete documentation index, see [llms.txt](https://docs.payerset.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payerset.com/readme.md). # Payerset Resource Center Documentation Overview Our mission is to empower healthcare organizations, insurance carriers, researchers, consultants, and data-driven professionals with the most accurate and comprehensive healthcare price transparency data on the market.\ \ This resource center is aimed to customers to have an understanding of the data structures, payer & provider compliance with the CMS mandates, and how to use the Payerset platform. If you have any questions or require further assistance, please reach out to . We are committed to delivering an exceptional experience and look forward to helping you unlock the true value of healthcare data for your organization.

	Cover image
Guides to Using Payerset	cropped-Group.png	Guides
Payerset Data Lake Resources	cropped-Vector1.png	Data Lake
Hospital Price Transparency MRF Resources	cropped-Group 437.png	Hospital Transparency
Payer Transparency Scorecard	cropped-check.png	Payer Transparency

--- # 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.payerset.com/readme.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.