> 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/aws/using-pump/credit-faq.md).

# Credit FAQ

**Question:** I have existing credits, can I use them with Pump?

**Answer:** Yes! We will be able to work with you.

**Question:** I just got an email about an invoice, but I have credits, where did they go?

**Answer:** If you believe you have credits not applied to your invoice, please email <billing@pump.co>.

**Question:** I believe I got the wrong amount of credits

**Answer:** You can see how many credits you have here: <https://app.pump.co/settings/credits>. If you don't believe this is the correct amount, be sure to check with the Account Executive who onboarded you.

**Question:** I got new credits after joining Pump

**Answer:** If you were awarded credits after joining Pump, Congrats! Please be sure to send proof to us, like a screenshot of the credits in the AWS console.

* Step 1: Go to the AWS Management Console
* Step 2: Go to [**Billing and Cost Management**](https://us-east-1.console.aws.amazon.com/costmanagement/home#/home)
* Step 3: Go to "Credits" on the left menu.

You should be able to send a screen recording of the credits there.


---

# 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/aws/using-pump/credit-faq.md?ask=<question>&goal=<user_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.