Billing

Manifest Platform uses a credit-based billing system. All resource consumption -- LLM calls, compute, storage, data transfer -- is metered and charged against your organization's credit balance.

Credit System

Credits are the universal unit of account on the platform. Rather than tracking separate bills for each service (LLM tokens, compute hours, storage GB), everything is converted to credits at well-defined rates.

How Credits Work

flowchart LR
    Purchase[Purchase Credits] --> Balance[Credit Balance]
    Balance --> Usage[Resource Usage]
    Usage --> Transaction[Credit Transaction]
    Transaction --> Debit[Debit from Balance]
    Debit --> Balance

1. Your organization purchases credits (or receives them as part of a subscription).
2. As you use platform resources, each operation is metered and converted to a credit cost using the active rate card.
3. A credit transaction is recorded with full attribution (who, what, when, how much).
4. Your balance is debited accordingly.

Checking Your Balance

Navigate to Admin > Billing to view your organization's credit balance. The dashboard displays:

• Credit Balance Card -- Shows credits remaining, total purchased, and lifetime consumed
• Balance Progress Bar -- Color-coded to indicate health: green (>50% remaining), yellow (25-50%), red (<25%)
• Status Badge -- One of: Healthy, Low Balance, Critical, or Overdrawn

The balance card updates in real time as your organization consumes credits.

Usage Tracking

Every billable operation creates an immutable credit transaction in the ledger with multi-level attribution.

Transaction Fields

Field	Description
credits_debited	Number of credits charged
service_type	What type of operation (llm_call, data_transfer, agent_runtime, etc.)
resource_type	What resource was used (workflow, agent, connector, dataset)
resource_id	ID of the specific resource
user_id	Who triggered the charge
workspace_id	Which workspace
usage_quantity	Raw usage amount (tokens, GB, hours, etc.)
usage_unit	Unit of measurement (tokens, GB, hours, executions, calls)
rate_applied	Credits per unit charged
balance_before	Balance before this transaction
balance_after	Balance after this transaction

Viewing Transactions

The Admin > Billing dashboard includes a full transaction history table. For each transaction you can see:

• Date -- When the charge occurred
• Service Type -- Color-coded badge (e.g., LLM call, data transfer, compute)
• Credits Debited -- Amount charged
• Resource -- Type and name of the resource that incurred the charge
• Balance After -- Running balance after the transaction

Use the period selector (7d, 30d, 90d, all-time) to filter the view, and pagination controls to navigate through history.

Attribution Hierarchy

Transactions support hierarchical cost roll-up through the parent_transaction_id field. For example, a workflow execution might create a parent transaction, with child transactions for each LLM call and connector invocation within the workflow:

Workflow Execution (parent)
  ├── LLM Call: GPT-4o (child)
  ├── Connector: PostgreSQL query (child)
  └── LLM Call: Embedding (child)

This enables drill-down cost analysis from organization level down to individual operations.

Usage Breakdown

The billing dashboard provides visual breakdowns of your credit consumption:

• Burndown Chart -- Area chart showing credit consumption trend over time
• Service Breakdown -- Pie chart showing consumption by service type (LLM calls, compute, data transfer, etc.)
• Workspace Breakdown -- Pie chart showing consumption by workspace
• User Consumption Table -- Detailed table showing per-user credit usage

My Usage

Navigate to Admin > Billing > My Usage to view your personal credit consumption across all organizations you belong to. This view includes:

• Summary Cards -- Total credits consumed, number of organizations, service types used
• Consumption Trend -- Area chart showing your daily consumption pattern
• Organization Breakdown -- How your usage is distributed across organizations
• Service Type Breakdown -- Which services you use most
• Recent Transactions -- Your personal transaction history with pagination

Rate Cards

Rate cards define the pricing rules for each service type. They determine how raw usage (tokens, GB, hours) converts to credits. Your organization's active rate card is set as part of your subscription.

Pricing Models

Model	Description	Example
passthrough_plus_markup	Provider cost + percentage markup	LLM calls: provider cost + 15%
flat_rate	Fixed credits per unit	Compute: 2 credits per hour
tiered	Different rates at different volume levels	Storage: 1 credit/GB for first 100GB, 0.5 credits/GB after
formula	Custom calculation	Dynamic pricing based on complexity

The rate applied to each transaction is recorded in the transaction record, so you can always see exactly how a charge was calculated.

Rate Card Lifecycle

Rate cards have effective_from and effective_until dates. When a new rate card is activated, the previous one's effective_until is set. Historical transactions always reference the rate card that was active at the time of the charge, ensuring billing accuracy even when rates change.

Purchasing Credits

Credits are provisioned as part of your subscription plan or purchased through your account team. Contact your Customer Success Manager (CSM) to purchase additional credits or adjust your credit allocation.

Your current balance and purchase history are visible on the Admin > Billing dashboard.

Alerts and Notifications

The billing system monitors credit consumption and triggers alerts based on configurable thresholds.

Alert Types

Alert	Severity	Trigger
low_balance	warning/critical	Credits remaining below threshold
high_burn_rate	warning	Daily consumption rate is unusually high
anomaly	warning	Spending pattern deviates from historical norm
projected_depletion	info/warning	Projected date when credits will run out

Alert Display

Active alerts are displayed on the Admin > Billing dashboard with severity-based styling:

• Healthy (green) -- Balance is above threshold
• Low Balance (orange) -- Balance has dropped below the configured threshold
• Critical (red) -- Balance is less than 50% of the threshold
• Overdrawn (red) -- Balance is negative

Alert recipients are shown on the dashboard. Contact your organization administrator to update alert thresholds or recipient lists.

Subscription Management

Subscriptions control which platform features your organization can access and may include bundled credit allocations.

Subscription Fields

Field	Description
product_name	Subscribed product tier
status	active, trial, suspended, cancelled, expired
billing_cycle	monthly, annual, or custom
start_date / end_date	Subscription period
trial_end_date	When the trial expires
auto_renew	Automatic renewal
quantity	Number of seats or units

Subscription details are managed through the Admin > Billing UI.

Budget Tracking

Organizations can set a budget for a contract period to track spending against allocation. With budget and contract dates configured, the billing system calculates:

• Burn rate -- average daily credit consumption
• Projected depletion -- estimated date credits will run out at current rate
• Budget utilization -- percentage of budget consumed vs. time elapsed in the contract

This data powers the burndown charts on the billing dashboard and drives proactive alerts when spending trends indicate the budget may be exceeded.