> ## Documentation Index
> Fetch the complete documentation index at: https://docs.prophecy.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Credits

> How credit consumption in Prophecy corresponds to platform usage

<Callout icon="/images/icon.png" color="#FFC107">
  Credits apply to the [Free and Professional Editions](/administration/platform/editions) only.
</Callout>

In Prophecy, **credits** represent a unified measure of usage across the platform.

Plans, teams, and fabrics define how billing and credit consumption are organized.

* A plan is the top-level billing unit. Each plan includes exactly one team.
* A [team](/administration/management/teams/teams) represents a group of users who share access to resources through one fabric.
* A [fabric](/data-analysis/environment/fabrics/prophecy-fabrics) points to a dedicated Prophecy warehouse database and compute resources.

<Info>
  To learn about monitoring credit usage and buying additional credits, see [Usage and
  billing](/administration/management/usage-billing/usage-billing).
</Info>

## How credits are charged

The following actions consume the corresponding number of credits.

| Action            | Description                                              | Credits Consumed |
| ----------------- | -------------------------------------------------------- | ---------------- |
| **Team Members**  | Number of users allowed on your plan                     | 20 / user        |
| **AI Requests**   | Each time you click on Copilot or interact with an Agent | 0.04 / request   |
| **Compute**       | Processing required when running a gem or pipeline       | 3 / CPU hour     |
| **Data Egressed** | Data sent outside the Prophecy warehouse                 | 0.045 / GB       |
| **Data Storage**  | Data stored in the Prophecy warehouse                    | 0.02 / GB        |

<Note>
  The Prophecy warehouse is powered by DuckDB. Advanced users can update the DuckDB SQL queries in
  the **Code** view of their project to optimize computation and reduce credit consumption.
</Note>

## Relationship diagram

The following diagram shows how credit consumption actions relate to plans, teams, and fabrics.

```mermaid theme={null}
flowchart LR
A[Plan] --> B[Team]
B --> C[Fabric / Prophecy Warehouse]

subgraph "Credit Consumption"
direction LR
E[Team Members]
F[AI Requests]
G[Compute]
H[Data Storage]
I[Data Egressed]
end

B -.-> E
C -.-> F
C -.-> G
C -.-> H
C -.-> I

%% Styling
classDef entity fill:#f5f5f5,stroke:#bdbdbd,stroke-width:1px,color:#1c1e21
classDef metric fill:#e1f5fe,stroke:#bdbdbd,stroke-width:1px,color:#1c1e21
classDef cluster fill:transparent,stroke:#bdbdbd,stroke-width:1px

class A,B,C entity
class E,F,G,H,I metric
```

## What happens when you run out of credits?

When you run out of credits, the following features will be disabled:

* Prophecy Agent
* Interactive pipeline runs
* Scheduled pipeline runs
* Project publication (deployment)