> For the complete documentation index, see [llms.txt](https://wiki.lucysecurity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.lucysecurity.com/application-reference/settings/clients/client-invoices.md).
# Client Invoices
Introduction
Each time you add to your workstation's balance Lucy generates an invoice for the transaction. These invoices are available to view and download on this page.
{% hint style="info" %}
Navigate to **Support -> Client Invoices**
{% endhint %}
***
## Refilling your workstation's balance
The balance on your workstation can be used to purchase domains and send SMS. You can refill this balance on your **License** page and clicking **Add Balance**:
### Payment options
You can add to your workstation balance using Stripe or by arranging a wire transfer through your Account Manager. Lucy creates a PDF invoice automatically that is added to your Client Invoices page.
---
# 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://wiki.lucysecurity.com/application-reference/settings/clients/client-invoices.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.
