> For the complete documentation index, see [llms.txt](https://help.pump.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.pump.co/home/pumps-knowledge-base.md). # Pump's Knowledge Base Explore our knowledge base for all the right answers, your go-to resource for all things Pump! Welcome to the Pump documentation hub! Find everything you need to manage your cloud financial operations with ease. Our articles, clear guides, and step-by-step instructions help you make the most of the Pump platform. Whether you're just getting started or optimizing your workflows, our goal is to empower you with the knowledge to take full control of your cloud costs. We optimize your cloud spend on AWS, GCP, Azure with our savings commitment planner, infrastructure recommendations, and more! ### How Pump Works Pump sits between you and your cloud provider as an optimization and billing layer. Here's the short version: 1. **Connect Your Cloud:** Link your AWS, GCP, or Azure accounts. Pump starts analyzing immediately, no agents to install, no infrastructure changes, no engineering lift required. 2. **Savings, Visibility, Intelligence:** View all your cloud spend in one pane of glass. Pump automatically flags savings opportunities, cost anomalies, and more while enabling you to save money using our AI-driven commitment purchasing and group buying power. 3. **Optimization & Confidence:** Track all your cost savings over time, develop incredible savings reports, and feel confident about the next quarter. Pump's savings engine optimizes in the background even when you aren't so your team can focus on building. ### Have questions? Reach out to our team at **** - we typically respond within a few hours! --- # 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://help.pump.co/home/pumps-knowledge-base.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.