Skip to main content
Plan & Billing is where an organization sees its commercial standing: the Terms it has accepted, how it pays, the plan it is on, the offer it can accept, its renewal, its recent invoices and the one next step, if any, that keeps billing in good standing. In an agent host it is a Page, and every fact the Page shows is also available to an agent through get.

Open the Page

Call open_plan_and_billing. It takes no input. It is available to Buyer, Seller and Organization accounts. An Agents account has no plan of its own, because its organization holds it, so open_plan_and_billing refuses it with WRONG_ACCOUNT. In the web app, Plan & billing in an Agents account says which organization manages the plan and billing. A person who administers that organization can switch to its account and open Plan & Billing there. The opening call changes nothing. The Page reads the organization of the selected account itself, so you do not pass an organization. To show a person their plan options, open this Page: it lists the plans and records the one they choose. An agent does not need a separate call to display plans. open_page with { "page": "plan_and_billing" } still opens the same Page for now, and its answer names open_plan_and_billing for a host that showed nothing. A person can do the work that needs a human in the Page: review and accept the current Terms, choose a plan, decline the offer or decide later, cancel the plan at term end or reinstate automatic renewal, ask us for help choosing a plan, enter or change the invoice details (the payer details), set up card payment, and set up where a Seller is paid. The Page makes the same save_billing calls an agent makes, and a plan the person chooses there is recorded for the organization the Page names. It shows the plans only when the server says choices show, and it asks the person to confirm the plan and the payment schedule before it records anything. A plan binds the organization, so choosing one does not put it in force on the call: it records an approval that a direct administrator of the organization confirms on Apostra. The Page opens that approval page, and the plan shows on the Page once it is approved. If the offer changes while the person is choosing, the server refuses the stale choice and nothing is recorded. The Page reloads the offer, says what changed for the plan the person picked (the monthly commitment, the included IUs, the price per extra IU, a payment schedule, or that the plan is no longer offered), or that nothing changed for it, and asks them to confirm again. It keeps the plan and schedule they picked while they are still offered. Bank details are typed into the Page and never pass through the model. The invoice details are in the Page’s Payer details section. Until something is entered it says what an invoice needs (a payer name, street address and country) and offers Add payer details. Once details are on file it shows them the way they print on an invoice, leaves out any field that is empty, and says whether they are complete. When they are not, it names only the fields the server lists in payer.missing, for example “An invoice still needs a street address and country.” An organization administrator can change them there: the Page checks what they type the way the server does, sends only the fields they changed (null for a field they emptied) and the details save straight away. An agent saves them the same way, with save_billing and payer; see Change the payer details. Someone who is not an organization administrator sees the details and no button. If a credential may not read some of them, the Page shows the rest and says some are hidden. The Media billing section shows who your media invoices are addressed to. Each entity shows its legal name, country, currency, address and invoice emails, whether a tax ID is on file, and the advertisers or accounts it bills, with the organization default marked. An organization administrator can add an entity, edit or remove one, make one the organization default, and attach one to an advertiser or a child account, or detach it. The Page looks advertisers and accounts up by name, checks what they type against AdCP’s limits before it sends (a legal name up to 200 characters, a tax ID up to 30, a street up to 200, a city and a region up to 100, a postal code up to 20, and up to 10 invoice emails), and sends one change per click. Each change saves straight away, with no approval link. When the server refuses a change, for example removing an entity that still has attachments, the Page shows the reason. An agent makes the same changes with save_billing and mediaBilling; see Media billing entities. Someone who may not change billing details sees the entities and no buttons, and a credential that may not read some details sees names and flags only. The section appears when the server allows the caller to read media billing, and invoices do not use these entities yet.

Read billing from an agent

get with { "kind": "billing" } returns the organization’s billing in one read. It takes no ID, filter or include. It always reads the organization of the selected account, so check object.organization.customerId before you act on it. Billing: plan and invoices lists every field. Start with nextAction: the server names the next step, so a caller never works it out from raw fields. nextAction.type is NONE when nothing is owed. Any other type is the step to take, in this order: accept Terms, accept the governing agreement, choose a plan, add billing details, then set up payment. nextAction.severity is success or warning, and nextAction.canCompleteInChat is true only when the step is accepting Terms and the signed-in person can do it from this session.

What you can do

Every write needs an authenticated user with direct authority on the organization. A direct organization administrator may work from the organization account or any child account they administer. An administrator of a child account who is not a direct organization administrator does not have authority over its parent organization. A write that names a Terms version is refused when that version is no longer current, and nothing changes. Read again, then ask the person to review the new version.

Add billing details

Billing details are the payer name, billing contact and address that invoices and card receipts go to. nextAction.type is ADD_BILLING_INFO until they are on file. In the Page, the Add billing info button opens the invoice details form in place, and the details save straight away. An agent calls save_billing with payer and the details save the same way; see Change the payer details. The details can also be entered in the Apostra web app, under Settings → Plan & Billing → Payment & invoices. permissions.canEditBillingInfo says whether the signed-in person may change them.

Add or remove a card in the web app

The Apostra web app adds and removes cards with the same calls, under Settings → Plan & Billing → Payment & invoices. The administrator is already signed in on Apostra, so the screen records the approval for them in the same step. Adding a card opens the secure card page in a new tab, where the card is entered (it is never entered in the web app), and the screen shows the card once it is confirmed. Removing a card asks for the removal and shows it as removed once it is approved. When the screen cannot record the approval, because the signed-in person is not a direct administrator of the billing organization or the decision fails, it shows the approval link instead, and an administrator approves the change there. Nothing changes until it is approved.

When another organization manages billing

A member of an account whose organization manages its billing, and who is not one of that organization’s administrators, does not get a failure from the read. get returns the organization that manages billing and changeableBy: "organization_administrator", and the Page shows the same message. Only an administrator of the managing organization can view or change its billing. See Response variants.

Support sessions

Apostra staff working in a customer’s account through a support session, read-only or elevated, read all of Plan & Billing: the plan and its term, payment terms, plan charges, media spend, Rate Card, plan history, invoices, usage and the payer details, so they can see which plan a customer is on and help the customer move to the right one. The read works from the organization and from any of its accounts. What a support session may not change is in permissions.supportSessionLimit (absent for everyone else), and the Page and the widget withhold those controls and say why. The server decides it; a client only renders it.
  • read_only: a read-only session changes nothing. Every plan and billing change is refused with ACCESS_DENIED, details.reason: "billing_change_unavailable_in_support_session" and details.nextAction: "ask_account_admin", and the Page shows “Support sessions can’t change plans or billing.”
  • no_plan_changes: an elevated session keeps the write access it has, except that it never changes a plan. Accepting or switching a plan, answering its offer and changing its renewal are refused with the same reason and the message “Plans can’t be changed in a support session.” The Page withholds those controls and says so.
Accepting the Terms is refused for staff in every session. Retrying does not change an answer. An administrator of the account makes the change signed in as themselves.

Plans and pricing

How plans, included IUs, the IU price and renewal work is described in Organization IU Rate Card. The read returns the plan in force, an accepted plan that starts at the end of the term, and the offer the organization can accept at its exact version.

Plan charges and media spend

Plan & Billing shows two rows for how money moves, and the read decides both.
  • Plan charges says how the plan in force charges the organization. On the Standard plan it reads “Card, billed monthly for IUs used”, and plan.charges is card_monthly_usage. Other plans have no description yet, so plan.charges is null and the Page shows no Plan charges row.
  • Media spend says how the organization pays for the media it buys: Prepay when it must fund a balance first, Credit when it pays on terms (standing.mediaSpend is PREPAY or CREDIT). Only an organization that buys media has media spend, so the read sends standing.mediaSpend as null for one that does not, and the Page and the web app show no row for null. A seller that buys no media sees no Media spend row.

The separate plan task is retired

Plan & Billing is the one place a plan is chosen, switched or renewed. The older IU plan widget and its v2 tools are retired: open_iu_plan_task, get_iu_rate_card_offer, accept_iu_rate_card_offer, record_iu_rate_card_offer_response, request_iu_plan_help, schedule_iu_plan_non_renewal, reinstate_iu_plan_renewal, their storefront-named aliases and v2 add_payment_authority. The routes behind them, /api/v2/billing/iu-rate-card/mcp-app/* and /api/v2/billing/storefront-rate-card/mcp-app/*, are retired too. Each answers GONE with a pointer to the V3 tool that replaces it: get with kind: "billing", save_billing, save_ask, or request_payment_authority then confirm_payment_authority. A plan change and a card setup return approval_required with a link, and nothing changes until a direct administrator of the billing organization approves it on Apostra.

What you pay as a buyer

A buyer plan has no monthly charge. You pay for each Intelligence Unit (IU) your activity uses. The figures below are from the current Rate Card. The live Rate Card is the authority, and your own terms can differ (see The published Rate Card). The two plans cost the same and carry the same activity charges, so the choice does not change what you pay. Business Manager is the plan the pricing documentation names for agencies and teams that run many brands, on one IU bill for the organization. The price is set in your organization’s currency. It is published in each currency, not converted from dollars. Neither plan limits how many Buyer Accounts your organization holds. Creating accounts is limited to 25 in any 24 hours.

What uses IUs

Three activities have a price. Everything else costs nothing, including connecting an account, discovering accounts, mapping them to advertisers and reading your own data. A billing period is one month of your organization’s IU billing cycle, measured in UTC. See How IU billing works for when a buy counts, with worked examples.

What you are not charged

Under the current Rate Card, Apostra takes no percentage of your media spend, adds no card processing fee, and gives no setup credit. A buyer agreement you accepted earlier keeps its own terms. The IUs pay for Apostra’s platform. The media itself is priced by the seller and billed on the route you chose for that seller. The seller’s price is separate from your IU charges.

Private offers

If you want terms the public plans do not carry, such as a monthly commitment with included IUs, ask for a private offer. Call save_ask with type: "commercial", as in What you can do. You can also choose Get in touch in the Plan & Billing Page. A private offer comes from one revision of the Rate Card, and you can accept it only while that revision is in effect. Once that revision ends, the offer no longer applies: if you have no plan, Plan & Billing offers the public plans instead and asks you to choose one. Ask for a new private offer if you still want custom terms. The public Rate Card is at app.apostra.com/rate-card. For more detail, see the Organization IU Rate Card. For the plan a new organization takes at sign-up, see The Standard plan.

What you pay as a seller

A seller plan has no monthly charge either. The figures below are from the current Rate Card. The live Rate Card is the authority, and your own terms can differ. The columns are plans, not account types. Under the Listing plan a seller pays nothing: no plan charge and no activity charge. Under the Storefront agent plan, the seller pays for the brief responses and media buys its hosted agent handles, in a billing period of one month of its IU billing cycle. The buyer pays its own IU for the same media buy on its own plan. A plan’s own terms apply to every Seller Account of the organization, whatever its account type. A plan that predates Standard keeps the terms its own row states, so your terms can differ from this table. Only the Standard plan prices an activity by account type: it charges each metered activity by the type of the account that incurred it, a Listing account has no charged activities, and a Storefront account is charged at the plan’s rate (see How the account type affects what you pay). Enhanced Reporting is not a seller charge. It is charged to the organization that owns the connected ad account (see What uses IUs). Selling on Apostra needs no paid AgenticAdvertising.org (AAO) membership, and Apostra charges nothing for AAO. A seller on the hosted Storefront agent has nothing to do. A seller that connects its own sales agent declares it in its brand.json or trust.json, or adds a community entry for it in the AAO registry (see Registering your agent with AAO).

Before your storefront answers a charged brief

When your plan charges for brief responses, the storefront that handles a brief must meet two prerequisites before it answers:
  1. Brief Acceptance rules. The storefront has a live Brief Acceptance policy in AI Business Rules, or you have turned Brief Acceptance off, which still counts as set up. Saving and testing your rules is free.
  2. Payment is covered. Your organization has a payment method on file or approved credit, or your plan carries a monthly commitment.
Until both hold, the brief is refused before any work starts, with INVALID_REQUEST, details.reason seller_prerequisites_missing and a details.missing list (brief_acceptance_rules, payment_authority, or storefront_unmatched when the brief’s storefront is not yours). The buyer is told only that you have not finished setting up. A brief from a sandbox advertiser is never charged and needs only the Brief Acceptance rules (see Sandbox advertisers and live spend). Apostra turns this refusal on per seller; until it is on for you, each check is counted and the brief is answered. What you are charged follows the plan your organization accepts. Which plan sets which features is described in Your plan decides what you pay, not what your account can do.

Worked examples

These examples price each IU at the Standard plan’s list price in dollars, which What you pay as a buyer gives for each currency. The live Rate Card is the authority (see The published Rate Card).

What is a media buy, and what does it cost

A media buy is an object in Apostra: one buy placed with one seller. A campaign creates one or more of them, and Apostra creates one media buy for each channel group, seller and settlement currency (see Why groups create media-buy boundaries). So one campaign across five sellers creates five or more media buys, and one seller can hold one, three or five of a campaign’s media buys, depending on how many channel groups and currencies the campaign uses. A channel group can list one channel or several, so a media buy covers one channel or many. A billing period is one month of your organization’s IU billing cycle. A buy that was already running is not charged for a new period it only spills into for less than 24 hours, and the first period a buy is active always counts, however short.

What Enhanced Reporting is

Enhanced Reporting is a control on one connected ad account, such as one Meta ad account. Turn it on for the account and, once the account’s reporting has synced, Apostra charges 4 IUs for that account in each billing period, $20 on Standard. It is charged to the organization that owns the connected account, per account and not per campaign, so a second campaign on the same account adds nothing, and an account you do not turn it on for is never charged. A Listing account cannot use it. Standard campaign reporting is separate and free.

Five sellers, one campaign

A campaign buys from five sellers, all in one channel group and one currency. That is five media buys. Active for one billing period, they cost 5 × 1 IU = 5 IUs, or $25. If the campaign uses two channel groups and every seller sells into both, it creates ten media buys and costs 10 IUs, or $50 for the period. The number of sellers does not set the charge. The number of media buys does.

One campaign across Meta, TikTok and ChatGPT for three months

The campaign buys from three sellers, Meta, TikTok and OpenAI Ads (the seller behind ChatGPT ads), in one channel group and one currency. It is placed as three media buys, each accepted by its seller, and runs through three whole billing periods. There is no single three-month billing period: each month is charged on its own. Enhanced Reporting adds to this only if you turn it on. With it on for the one connected ad account at each platform, it adds 3 accounts × 3 billing periods × 4 IUs = 36 IUs, or $180, for a total of 45 IUs, or $225. With it on for none of them, the campaign costs the $45 above. Two things change the count. A flight that starts mid-month touches four billing periods instead of three. A campaign split into two channel groups creates six media buys, so the media-buy line doubles to 18 IUs, or $90. The media itself is separate. Each platform sells it at its own price, and the IUs are Apostra’s charge for the platform. See What you are not charged.

The published Rate Card

The Terms (section 10) say the current Rate Card is available at all times, including before you choose a plan. Anyone can read it, without signing in, at app.apostra.com/rate-card. It is also linked from the Account menu. The same Rate Card is available to an agent or script:
The answer comes from the same published Rate Card revisions billing uses. It has three parts: Each revision gives its publicVersion, name (a label built from the effective date, such as IU Rate Card effective 2026-10-21), effectiveDate, endDate (when it stops applying, or null), publishedAt and noticeSentAt (when written notice of it went out, or null). Its plans are the public plans, each with its included IUs, rollover, payment terms, activity schedule, and a prices list: the plan’s own currency first, then every other currency it is priced in. Amounts are in minor units, so 500 in USD is $5.00. Its activitySchedule lists the IU charge for each activity. Only public plans at list price are shown. Private plans, plans offered to one organization, discounts and codes never appear; your own terms are in Plan & Billing. A revision terminated on the day it would have taken effect is left out, because it never applied. The answer can be up to a minute old. An upcoming revision changes a Standard plan at that plan’s next renewal on or after its effective date, once its notice is at least 30 days old. Nothing already metered or committed changes.

Your plan decides what you pay, not what your account can do

A plan sets your price, commitment, included IUs, payment terms and renewal. It does not set which features your account has. Accepting, switching to or renewing a plan gives your account no feature profile, and it does not end a feature profile that Apostra staff granted by hand. What your account can do comes from three things:
  • Its account type. A Seller account is a Listing or a Storefront, and that decides its seller features (see Account type). Every buyer account starts on the buyer experience profile when it is created, on every plan including Free.
  • Its add-ons, such as Distribution.
  • Beta access, which keeps applying until it ends.
Two things to know while Standard is not yet the only plan. Accepting a plan that is a Listing plan or a Storefront plan still sets the account type of your organization’s Seller accounts. And a feature profile that a plan gave your account before this change stays until the end of the plan term it was given for. Renewing the plan does not extend it. If you are unsure what your account has, ask your Apostra contact before you accept.

What stays out of an agent call

Card numbers, processor secrets, setup tokens, hosted payment links and bank details never appear in a read or pass through the model. Public Terms and documentation links do appear.