> For the complete documentation index, see [llms.txt](https://docs.scraperapi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scraperapi.com/responses-and-formats/output-formats.md). # Output Formats If you have specific project needs, that require you to parse the data you get back from us or transform it into a more r**eadable or structured format**, you are in the right place. The portfolio of output formarts that our product supports is growing, as we aim to ensure we meet your diverse project requirements and the evolving industry standards. The subpages below go into detail about our existing output formats, where they apply, and which ones are best suited for your needs. #### **Autoparse Parameter** 👉 Simply parse your data with one parameter - `autoparse=true`. 👉 Get your parsed results in structured `JSON` or `CSV` for a list of domains by setting `output_format=json` or `output_format=csv`. Read more about available domains [here](/responses-and-formats/output-formats/json-response-autoparse.md). #### **Available Output Formats** 👉 Get response in LLM friendly structure with the output formats `markdown` or `text` for every URL on the web. Read more [here](/responses-and-formats/output-formats/llm-output-formats.md). --- # 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.scraperapi.com/responses-and-formats/output-formats.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.