> For the complete documentation index, see [llms.txt](https://gaffa.dev/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gaffa.dev/docs/credits-and-pricing.md).

# Credits and Pricing

{% hint style="info" %}
View our current pricing plans on the Gaffa [homepage](https://gaffa.dev/#pricing)
{% endhint %}

## Browser Requests

Browser requests are charged in terms of credits based on the following factors:

* **Request length:** Billed at 1 credit per 30 seconds, the request takes to run on the browser.
  * If screen recording is enabled, this is doubled to 2 credits per 30 seconds.
* **Proxy bandwidth usage:** All requests that use a `proxy_location` parameter use our network of residential proxies and are billed at 750 credits per 1GB of bandwidth used.
* **Paid Actions:** Some actions will incur additional costs for their usage in a browser request. These are:
  * [JSON Parsing](/docs/features/browser-requests/actions/parse-json.md)

Each successful request will deduct the corresponding number of credits from your monthly allowance. Be sure to use as many of your monthly credits as you want, as they don't roll over month to month.

## Mapping Requests

Mapping requests are also charged in credits at a rate of **1 credit per mapping request.**


---

# 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://gaffa.dev/docs/credits-and-pricing.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.