> 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/pump-view/how-pump-view-works.md).

# How Pump View Works

## How Pump View Works

Pump View is a spend observability layer that pulls billing data from every provider and service you connect, then surfaces it in one place. Instead of switching between the AWS Billing Console, GCP Billing Reports, Azure Cost Management, and individual dashboards for services like Anthropic or Datadog, you query everything from a single interface.

### What Pump View includes

| Feature        | What it does                                                                                                                                                                                     |
| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Playground     | Interactive query builder for exploring spend across all connected providers and services. Filter by service, account, region, SKU, usage type, and more using dropdown filters or SQL querying. |
| Reports        | Save any Playground query as a recurring report. Schedule delivery via email or Slack.                                                                                                           |
| Annotations    | Pin notes to your cost timeline to explain spikes, deployments, or team changes.                                                                                                                 |
| Budgets        | Set monthly spend caps scoped to specific accounts or services. Get alerted at custom thresholds.                                                                                                |
| Anomaly Alerts | Automated detection of unusual spend changes. Configurable alert channels.                                                                                                                       |
| Forecasting    | End-of-month spend projections at P50 and P90 confidence levels.                                                                                                                                 |
| Allocations    | Allocate costs using tags.                                                                                                                                                                       |

### What data Pump View pulls

Pump View ingests billing and usage data from every provider and integration you connect. It does not access infrastructure, workloads, or configurations.

| Provider | Data source                                     | Historical backfill on first connect |
| -------- | ----------------------------------------------- | ------------------------------------ |
| AWS      | Cost Explorer API, Cost and Usage Reports (CUR) | Up to 12 months                      |
| GCP      | BigQuery billing export                         | \~7 days                             |
| Azure    | Cost Management detailed cost reports           | Up to 90 days                        |

Third-party integrations (Anthropic, OpenAI, GitHub, Datadog, Cursor, ClickHouse Cloud) pull usage and cost data through each service's API. See [Integrations](/integrations/anthropic.md) doc for setup details per service.

Data refreshes daily across all providers.

### Multi-provider visibility

When you connect multiple cloud providers and third-party services, Pump View aggregates all of that spend into a unified view. The Playground lets you query across providers in a single session, so you can compare cloud costs alongside your Anthropic token spend or Datadog host charges without switching tools.

This is useful for teams managing workloads across clouds, or teams whose AI and DevOps tooling costs are growing alongside traditional infrastructure spend.

### How to get started

1. Connect at least one cloud provider or third-party service. See Getting Started help doc for the full setup flow.
2. Once connected, navigate to **View** in the left sidebar.
3. Pump backfills your historical data automatically. For AWS, this means up to 12 months of cost history is available immediately after connection.

No additional configuration is required. View is available on all Pump subscription tiers.


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.pump.co/pump-view/how-pump-view-works.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.