Billing & Credits

#Purpose

Your organization is a single tenant on Opal — the top-level container that represents your company and holds its members, teams, roles, resources, and organization-wide settings. Billing & Credits is the part of it that deals with money: what the organization is subscribed to, how it pays, and how it funds the work its people and agents actually run.

Those are two different questions, and Opal keeps them separate on purpose:

• What the organization is subscribed to — the billing profile, payment methods, the subscription plan, and the seats it holds.
• What funds the usage — the credit balance, and how it is topped up and monitored.

Both are managed in Organization Settings, the central area where an organization's profile and preferences, security, membership, teams and roles, billing, and credits are administered. Funding is not a separate system bolted on the side; it sits next to the rest of organization administration.

There is a practical reason to settle both early. A digital workforce is only useful if it keeps working, so the goal here is a setup you decide once and review occasionally — rather than a lapsed payment method or a balance nobody is watching. The plan also matters beyond finance: some capabilities are available only on particular plans, which makes it the answer surprisingly often when someone asks why a setting is not available to them.

This page is the map. It introduces the two pages in this cluster, explains how they fit together, and tells you where to start.

#In This Section

• Billing & Subscription — The organization's billing profile, payment methods, subscription plan, and seats, all managed in Organization Settings, and what the plan unlocks. Billing & Subscription
• Credits — How credits fund your organization's usage: the balance and its transactions, one-time top-ups, recurring credit subscriptions, automatic top-ups below a threshold, billing alerts, and what draws credits down. Credits

#Key Concepts

The subscription defines the plan; credits fund the usage. These are the two halves of the cluster, and an organization needs both: a plan that permits the work, and a balance that pays for it. The subscription is the commercial relationship — what the organization is subscribed to, how many seats it holds, and which capabilities that unlocks. Credits are the balance the organization draws on as work runs. They are complementary rather than interchangeable, and both are administered in Organization Settings.

The plan is one of the gates on what the organization can use. Some capabilities depend on the plan — for example, SAML single sign-on is available on the Enterprise plan only. That makes the plan a product decision as well as a commercial one. It is also only one of three gates: the plan, the role permissions granted to the person acting, and the permissions set on the individual resource. The full model is documented once, in Access & Permissions.

Seats belong to the subscription, not to membership. Deciding who is admitted to the organization is membership administration, covered by Members & Access. The seats the organization holds are part of what it is paying for, and are managed with the rest of billing. In practice the two are read together: membership tells you who is in, the subscription tells you what the organization is paying for.

Credits are held by the organization and shared across it. The balance sits at organization level, not per member or per space, so whatever members and agents do across the organization's spaces draws on the same balance. Credits can be added on demand, on a recurring cadence, or automatically when the balance falls below a threshold — and billing alerts keep the people responsible informed, so a falling balance surfaces on its own.

Cost visibility is not only an administrator's concern. Model token costs are expressed in Opal credits, and resources adopted from the Marketplace are charged in credits too — so builders see cost in the same unit finance manages while they are choosing a model or adopting a resource, which is where most cost decisions are actually made. Marketplace

Money flowing the other way is not billing. If your organization sells its own resources on the Marketplace, buyers pay in credits but selling organizations are paid out in US dollars. That side is covered by Payouts.

Prices, plan tiers, and credit rates are not published in this documentation. Check Organization Settings for what applies to your organization. Short definitions of the terms used here are in one place: Glossary.

#Where to Start

If you are setting an organization up, read the two pages in this order. The first establishes the plan the organization runs on; the second keeps the work funded.

1. Billing & Subscription — complete the billing profile, add a payment method, and confirm the plan and seats the organization holds, so the commercial side is settled and you know which capabilities the plan makes available. Billing & Subscription
2. Credits — fund usage from there: review the balance and its transactions, choose how credits are added, and switch on billing alerts so funding becomes something you review rather than monitor. Credits

If your organization is already running and you are here for one thing — updating a card, checking the plan, topping up the balance — go straight to the page that covers it.

If you are here because a feature is unavailable and you suspect the plan, read Billing & Subscription for what the plan gates, then Access & Permissions for the full access model.

For the rest of organization-level administration — the organization's profile and preferences, members and access, platform configuration, and governance — start from Organization.