> ## Documentation Index > Fetch the complete documentation index at: https://docs.hydrafetch.com/llms.txt > Use this file to discover all available pages before exploring further. # Blueprints > Complete pipelines that turn the endpoints into something useful, with the costs and the failure modes stated up front. The endpoint pages tell you what each call does. These tell you what to build with them. Every blueprint is a real pipeline: the sequence of calls, working requests, what it costs in credits, and the mistakes that are easy to make and expensive to find later. Each one ends with a brief you can paste into a coding agent, so you can hand the whole thing over rather than typing it out. ## Get data out of a site List a site's URLs, keep the ones worth having, and fetch them as clean Markdown ready to chunk. Point at a set of pages, describe the fields, get typed records instead of prose. Send a document URL to the same endpoint as a web page and get Markdown back, tables intact. Re-read the pages that matter on a schedule and diff the words rather than the markup. ## Answer questions and feed agents Search the web and get the pages back already fetched, so a model answers from text it can cite. Two tools, or one MCP connection, and your agent stops guessing from memory. ## Know who you are dealing with Start from a category and a city, and get a row per location with hours, services and a real address. Turn a column of domains into names, descriptions, industries, logos and socials. Read a customer's colours, fonts and logo from their own site instead of asking them to upload one. Render a mark for any domain straight from an image tag, with nothing to store or resize. ## Before you start Every blueprint assumes an API key in the `X-API-Key` header and a workspace with credits. If you have neither yet, [the quickstart](/quickstart) takes about two minutes. Failed calls never cost credits, so the cheapest way to understand any of these is to run the first step and look at what comes back.