> For the complete documentation index, see [llms.txt](https://developers.oxylabs.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.oxylabs.io/help-center/data-for-llms/do-you-deliver-data-in-an-llm-optimized-format.md). # Do you deliver data in an LLM-optimized format? Yes. [Web API](https://developers.oxylabs.io/products/web-api) gives you two ways to get data that models can use without manual reformatting. ### **Markdown output** Add `"output": ["markdown"]` to your `/scrape` request, and Web API returns the page content as Markdown. Markdown is lightweight, easy to read, and keeps a page's structure and emphasis. That makes it a good fit for chunking, metadata extraction, and preprocessing in AI workflows. See the [Scrape documentation](https://developers.oxylabs.io/products/web-api/scrape) for all output options. ### **MCP server** If you use an AI agent or coding assistant, you can connect it to Web API through our official Model Context Protocol (MCP) server. The server gives any MCP client, such as Claude Code or Cursor, search, scrape, and extraction tools it can call directly, with no custom integration code to write. See the [MCP server documentation](https://developers.oxylabs.io/ai-workflows/mcp) for setup. --- # 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://developers.oxylabs.io/help-center/data-for-llms/do-you-deliver-data-in-an-llm-optimized-format.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.