Documentation / Answers / Agent ownership and cost attribution: best practices

Agent ownership and cost attribution: best practices

Last reviewed Nov 18, 2026.

AI agents are becoming a workforce, and like any workforce they need someone accountable for them. An agent with no owner and no department is spend with nowhere to go: it can't be budgeted, charged back or explained at month end.

This guide sets out the practices we recommend for every company using Onaro Meridian, whichever registry your agents come from. It sits above the setup guide for each registry and the troubleshooting pages.

1. Every agent needs an owner and a department

Two fields decide whether an agent's spend is accountable:

  • Owner: the person who answers for what the agent does and what it costs.
  • Department: the budget the cost comes out of, and the line it lands on in chargeback and the general ledger.

Set both for every agent. In Meridian, the agent list shows which agents are missing either, and that list is the place to start each month.

2. Name agents so people recognize them

The name finance sees should be the name the business uses. "Invoice Agent" is clear; an internal ID or an auto-generated name is not.

  • Give each agent a clear display name in its registry. Meridian imports the display name.
  • Avoid relying on generated names. Some platforms create names automatically when they detect a runtime. Rename those at the source.
  • Use the description field for one sentence on what the agent does. It helps the person assigning an owner.

3. Tag owners and departments at the source

If your teams already maintain a registry, the easiest way to keep ownership current is to record it there. Meridian reads it during the daily import.

RegistryOwnerDepartment
Microsoft Agent 365Set the agent's owner in Microsoft. When that person is a member of your Meridian organization and the agent has no owner in Meridian yet, Meridian sets them as the owner.Assign in Meridian.
Google Agent Registry (early access)Not available from Google's registry. Assign in Meridian.Assign in Meridian. Reading a department label from the agent's runtime is planned.
AWS Agent Registry (early access)A tag named oasa-owner, or custom metadata text of the same name, containing the owner's email. One matching member fills a blank owner.A tag named oasa-department fills a blank department. Otherwise assign in Meridian.

A few rules apply wherever owners come from the source:

  • The owner must already be a Meridian member. Meridian never creates users or sends invitations from a registry. If the owner named at the source isn't a member, assign the agent in Meridian.
  • AWS: an oasa-owner email that matches exactly one member fills a blank owner. An email that matches no one, or more than one member, is kept beside the agent. Meridian does not create a user. What you assign in Meridian wins.
  • Don't put personal data in Google labels. Google's guidance is to keep names and emails out of labels. Use labels for things like cost centers instead.
  • Make the field required where you can. On AWS, a registry's metadata schema can require an owner before an agent is approved, which stops unowned agents at the door.

4. Or assign in Meridian

Every agent can be given an owner and department by hand in Meridian, from any registry. This is the right choice when:

  • the registry doesn't carry owners (Google today),
  • the owner in the registry isn't the person accountable for the cost,
  • or you'd rather manage ownership in one place.

What you assign in Meridian always wins. An owner from the source only fills in a blank. It never overwrites an owner someone set in Meridian.

5. Give agents a cost, even when the bill doesn't

Registries tell Meridian which agents exist, not what they cost. Many agents are paid for in ways a registry never sees: a flat vendor subscription, a contract, a per-user fee.

  • Measured spend comes in automatically from your connected AI providers, gateways and invoices.
  • Entered cost lets a finance admin record a cost for an agent directly, such as $400 a month for a vendor subscription, or a rate per run or per user. Entered amounts are always labeled as entered, never presented as measured, and measured spend for the same agent, vendor, and month replaces a listed vendor when it arrives, with the difference shown. Other vendor (not metered) is not replaced automatically. See Costs entered by finance.
  • Invoice splits let a finance admin divide one invoice line across several agents when adding billing data, by percentage or by amount. Percentages must add up to 100, or amounts to the line.

6. Connect with least privilege

Meridian only reads from your registries. Grant the smallest access that works:

  • Microsoft Agent 365: two read-only Microsoft Graph permissions, granted by a Global or AI administrator.
  • Google Agent Registry: a custom role with two permissions (list locations, list agents), or Google's Agent Registry Viewer role, on the project that holds your registry.
  • AWS Agent Registry (early access): the role MeridianAgentRegistryRead in your account, trusted to Meridian's broker with the external ID from the Settings card. The role can list and get registries and records, and list tags. It cannot create or approve records. Setup is Connect AWS Agent Registry.

You can stop any import at any time from its card in Meridian's Settings.

7. Retire agents properly

An agent that's no longer used should leave the books as cleanly as it arrived.

  • Retire it in the registry, so the daily import stops treating it as active.
  • Clear its budget in Meridian, so it no longer shows against a budget nobody manages.
  • Keep its history. Past spend stays on the record for audit.

8. A monthly checklist for finance

Once a month, before closing the period:

  1. Unowned agents: on Agents & allocation, look for a dash in Owner or Dept and assign one.
  2. New agents: review agents that arrived from a registry since last month.
  3. Budgets: check agents near or over budget, and their owners.
  4. Entered versus actual: review the variance where actual spend replaced an entered cost, and adjust the entry.
  5. Retired agents: confirm anything decommissioned has been retired at the source and in Meridian.

Questions? Contact support@onaro.io.