> For the complete documentation index, see [llms.txt](https://docs.biodock.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.biodock.ai/~/revisions/p7ymXsvCfFKfKgE1SN6X/user/usage-limits-and-team/run-credits-limits.md).

# Run credits limits

{% hint style="info" %}
If you are on a contract that bills based on analysis based on file size, this page does not apply to your organization.
{% endhint %}

Run credits are a consumable that can be used to initiate model training and analysis on Biodock.

### **Run credit consumption for analysis**

An analysis run consumes fractional run credits based on the # of images contained in the run, and the # of AI inferences (usually crops of size 1000, 2000, etc.) in the run.  See pricing table below, with graduated discounts shown.

This cost is additive, with total credits used = image credits + crop credits.

#### Credit pricing per image

| Base price | Over 1k images (60% off) | Over 5k images (80% off) |
| ---------- | ------------------------ | ------------------------ |
| 0.001      | 0.0004                   | 0.0002                   |

#### Credit pricing per crop

| Base price | Over 5k crops (75% off) | Over 100k crops (90% off) |
| ---------- | ----------------------- | ------------------------- |
| 0.0002     | 0.00005                 | 0.00002                   |

### Run credit consumption for training

Training jobs consume 0.5 run credits. If you expressly choose to add **both** region and object classes to one model (rarely the case), then training jobs consume 1 run credit.

### Tips for optimizing your credit usage

* Models trained with larger tile sizes use much fewer credits during analysis.
* Submitting many images at once, instead of one at a time, will help push more of your analysis into our discounted rates, saving credits.  It's typically much cheaper to run one very large job than 10 small ones (if it is large enough).


---

# 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://docs.biodock.ai/~/revisions/p7ymXsvCfFKfKgE1SN6X/user/usage-limits-and-team/run-credits-limits.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.