Skip to main content
The Organization IU Rate Card is the price list your organization will use for Intelligence Unit (IU) activity across Interchange. It applies once at the billing-organization level: buyer activity, storefront work, Murph, and other IU-rated capabilities draw from the same plan and wallet.
The standard IU Rate Card is published in staging for a controlled pilot and visible only to invited organizations. It remains unpublished in production until the pricing and governing terms are approved, so no organization needs to accept it in production today. Invited staging organizations can review and accept the exact effective revision. For invited organizations, Plan & Billing may show the accepted included-IU allocation, observed usage, and a display-only forecast. Transactional balance drawdown, entitlement enforcement, invoices, payment collection, and renewal charging remain off. Existing accepted media-pricing arrangements are unchanged.

The simple model

  • Connect at no cost. Connecting an account, discovering it, and mapping it to an advertiser do not consume IUs.
  • Pay for IU-rated use. When a capability has a published IU price, its usage draws from your organization’s one IU plan and wallet.
  • Commit for a volume discount. A monthly commitment lowers the effective price of the included IUs. Overage uses the metered rate.
  • Add a platform-license overlay when you need it. The optional license can cover contracted governance, integrations, support, and SLA. It sits on top of the same IU plan; it is not another wallet or a separate usage tier.
There is no separate buyer, storefront, Murph, or BYOBA plan. BYOBA—bringing or building your own buyer agent—is simply one way to use the platform.

One Effective Rate Card

The Rate Card shown for acceptance is the complete commercial result for your organization. It starts from a published standard plan and can incorporate one authorized adjustment source:
  • a corporate percentage adjustment;
  • a promotion or referral code;
  • a negotiated private package, such as 500 IUs for $500; or
  • an enterprise offer that combines a platform-access fee, an entitlement bundle, and included or specially priced activities.
These are not separate terms scattered across the product. A Commercial Offer or code distributes the terms; the resulting Effective Rate Card is what you review, accept, and later see in Plan & Billing. It is versioned and snapshotted with the binding so a later edit cannot rewrite what you accepted. Entitlements are enforced separately from billing, but the access bundle included in an enterprise offer appears beside its price.

Baseline plan sizes

The current staging-only pilot is modeled with these plan sizes: Pay as you go provides no included monthly IU allocation. Once production billing is enabled, commitments will be billed at the start of each monthly period; metered usage and committed-plan overage will be billed after the period. These figures and the IU denomination are not final. They are available only when an effective Rate Card is published in your environment and shown to your organization; they are not a production offer today. Your confirmation always shows the exact version, term, list price, and effective price that would bind you in that environment.

Pricing adjustments and private offers

If Scope3 has authorized a corporate discount for your organization, it applies once across the plan—not separately to buyer and storefront activity. Before you confirm, Plan & Billing shows the list price, discount, and effective price. Discounts do not stack. A negotiated package is shown as its own private Effective Rate Card, not as a second hidden discount. For example, an offer for 500 IUs at $500 shows that commitment, included quantity, and overage price directly. Enterprise offers can also show a monthly platform-access fee, the included access bundle, and activities that are included rather than IU-rated. Only one complete offer is effective for acceptance at a time. A later discount or Rate Card change never rewrites an accepted term. Changes apply through a new offer or successor term that you can review.

Rollover

On a committed plan, unused included IUs can carry into the next monthly period up to 50% of that next period’s included quantity:
  • the 250 plan can carry at most 125 IUs; and
  • the 1,000 plan can carry at most 500 IUs.
Carried IUs expire after that one successor period and cannot accumulate again. Pay as you go provides no monthly allocation to roll over. Setup and promotional credits never roll over.

Buyer social-account activity

Connecting and mapping a social account cost nothing. The current coarse-denomination planning value for explicitly activating a connected social account is 4 IUs per account-month. The denomination and final IU count will be set before production publication. The account-month includes:
  • mirror, read, and write access;
  • routine synchronization; and
  • up to 13 months of account history.
This is an activity price, not a buyer plan. Under the current pilot rendering, five activated accounts would attribute 20 IUs for the month to buyer social activity while still using the organization’s shared plan and wallet.
The activated-social-account meter remains in non-billing measurement. The current 4-IU planning value does not debit your wallet or appear as an invoice charge. Before charging can begin, Scope3 must finalize the denomination and activity count, publish the Rate Card in production, separately enable the billing systems, and your organization must accept the exact effective version.

Activities under calibration

Plan & Billing can also show the current starting hypotheses below. These rows are deliberately separate from the Published price list: they are not part of an accepted Rate Card, cannot debit your IU balance, and may change before a successor Rate Card is published. Documents, audio, and video appear together as content understanding, but they do not use one megabyte meter. Document pages/complexity and media duration are better cost and value boundaries than compressed file size. BigQuery is the exception because bytes billed directly drive the warehouse cost. Customer approval actions, retries, routing, caching, and internal model calls never create additional charges. Scope3-operated human work requires an explicit managed-service or statement-of-work price rather than an invisible per-approval IU charge.

New-storefront setup credit

When an effective Rate Card makes the offer available, a genuinely new seller billing account that completes storefront signup can receive one 100-IU setup credit. The credit is valid for 60 days from signup and is a restricted lot inside the organization’s shared wallet: it can be used only for eligible storefront setup work. Storefront provisioning may complete asynchronously without moving that expiry window, and later storefronts do not create additional setup credits. It cannot pay for buyer social-account activity, general Murph use, or another workload. It does not roll over, has no cash value, and does not stack. A valid promotion or referral code can attribute the same setup credit and may carry an authorized pricing or access adjustment. It cannot add a second setup credit or change the setup program’s value or expiration. The preview is recomputed after the code is entered, and the adjusted Effective Rate Card—not the code itself—is the accepted record. The setup-credit offer is available only within the controlled staging pilot; it is not currently available in production and does not create billable usage.

Acceptance and renewal

When an effective Rate Card is available, Settings → Plan & Billing shows:
  • the exact Rate Card version and effective date;
  • every eligible plan size;
  • your complete Effective Rate Card, including any corporate adjustment, promotion, referral, private package, platform fee, or included access;
  • included IUs, rollover, overage, billing timing, and term; and
  • the governing agreement and renewal posture.
After acceptance, invited staging organizations may also see the exact included allocation, remaining balance, overage rate, rollover policy, observed usage, and projected month-end usage on Usage & credits. These staging figures do not create charges or enforce entitlements. Only a verified organization administrator can accept a plan. An agent, API credential, service account, or impersonated support session cannot make that financial commitment. If the offer changes while you are reviewing it, the confirmation reloads and asks you to review the new version. Signup may present the current Terms of Service and IU Rate Card in one flow, but the acceptances remain distinct: the record preserves the exact agreement, Rate Card version, selected plan, complete adjustments, prices, actor, and time. An existing organization without a binding will receive the same Choose an IU plan action after a Rate Card becomes effective. Interchange never silently accepts a paid plan on its behalf. The plan task also lets an administrator Continue without a paid plan or Decide later. Continuing without a plan dismisses automatic login prompts for only the exact Rate Card revision reviewed; a successor revision may be shown again. Deciding later allows Interchange to show the task on the next login. In either case, Settings → Plan & Billing keeps the manual Choose an IU plan action available while the offer remains current, so you can return without waiting for another prompt. One acceptance binds the billing organization. If you accepted from a storefront task, the buyer view shows the same plan; if you accepted from a buyer task, the storefront view does too. Standard plans and private offers marked pin exact renew through immutable monthly terms at the accepted price. An offer marked review required stops before automatic renewal and requires a new explicit commercial decision. A later Rate Card or adjustment never silently reprices the current term. Ending the IU plan at term is an organization-wide decision: it prevents the next shared plan term from starting, rather than ending only one buyer or storefront capability. Individual capabilities are enabled or disabled separately.

Billing cycle and fee invoices

Once charging is enabled for your organization (it is switched on per organization, never silently — accepting a plan does not itself start charging), your IU plan bills on the calendar month:
  • Commitment at cycle start. The plan’s monthly commitment is charged at the start of each calendar month, at the price fixed in your accepted binding.
  • Overage during the cycle. Usage beyond your included and rolled-over IUs accrues as overage at your plan’s per-IU rate. For organizations paying by card, accrued overage is charged automatically once it crosses a threshold, so month-end never brings one large surprise; any remainder settles when the cycle closes.
  • A fee invoice at cycle close. Every charged month produces a numbered fee invoice — plan commitment, overage (IUs × rate), and payments applied — on Settings → Plan & Billing → Payment & invoices. Invoice numbers are sequential with no gaps, and an issued invoice’s charges never change; payments are appended as they settle.
Organizations paying by card are charged automatically against the saved card. Invoiced organizations receive the fee invoice only and pay on their existing terms — no card charge is made. If a card charge fails, the standard payment recovery ladder applies: retries on a published schedule, email notices, and a self-serve pay now action on Plan & Billing that clears everything instantly once it succeeds. While a failure is unresolved — or if accrued, uncollected overage reaches your account’s cap — new paid platform activity is held; viewing, reporting, exporting, and fixing your payment method are never blocked.

For agents and API clients

GET /api/v2/billing/iu-rate-card is the canonical organization offer read. GET /api/v2/billing/fee-invoices lists the organization’s fee invoices, and GET /api/v2/billing/fee-invoices/{invoiceNumber} returns one invoice with its line items. Agents should use the typed get_iu_rate_card_offer tool to open the same portable plan-selection task rather than reconstructing it from a generic API call. Acceptance and renewal changes are direct human commitments. The task invokes app-only operations to append the displayed, declined, deferred, or accepted outcome and to schedule or reinstate renewal. Every response is idempotent and tied to the exact Rate Card revision; an accepted outcome links to the immutable binding. These commit operations are not model-visible. The older storefront-rate-card REST paths and storefront-named tools remain deprecated compatibility aliases; new clients should use the organization IU names.

Separate from media pricing

IUs price platform activity. Existing media-pricing arrangements cover media spend and their accepted contract fee terms. This Organization IU Rate Card does not replace, amend, or silently remove those terms. Plan & Billing can show both because an organization may owe both platform/IU charges and media charges, but each is a separate commercial stream.

Plan & Billing

Where organization administrators review commercial terms

Storefront billing

Payouts, settlement, and the storefront view of the shared plan