Google Agent Registry Now Feeds Onaro Meridian

Last week we connected Onaro Meridian to Microsoft Agent 365. This week, Google.

Meridian now reads Google Cloud's Agent Registry, the directory of agents your teams build and run on Google Cloud. The agents in it come into Meridian, where finance can give each one an owner, a department and a budget.

That makes two of the three major clouds. Wherever your agents are built, they should end up in one place where their cost is accounted for.

Why a registry matters to finance

A registry answers "which agents do we have?" Finance needs the next answers: what does each agent cost, who owns it, and whose budget does it come out of?

Agents built on Google are paid for in model usage, mostly through Vertex AI, and that cost lands on a cloud bill that doesn't say which agent spent it. A list of agents is the first half of the answer. Meridian is where the second half lives: it attributes, controls and books what AI agents spend.

How it works

1. An admin connects a Google Cloud project. In Meridian, under Settings, Google Agent Registry, the card shows Meridian's service account. In Google Cloud, you grant that account read-only access to the project that holds your registry: a custom role with two permissions (list locations, list agents), or Google's Agent Registry Viewer role. Then you paste your project ID into Meridian.
2. Meridian checks the connection up front. One click confirms the project, its locations and its agents, so problems show up during setup instead of failing quietly later.
3. You preview before anything is written. Preview lists the agents Meridian found and changes nothing.
4. Your agents come into Meridian daily. Once a day, Meridian reads the registry and brings in new agents with their name, framework and runtime. We tested it end to end in production this week: an agent registered in Google Cloud appeared in Meridian's agent list.
5. Finance takes it from there. Google's registry doesn't name an owner, so you assign one in Meridian, along with a department. From there, budgets, alerts and chargeback work the same as for every other agent, and the cost flows into the journal entries Meridian posts to your general ledger.
6. You stay in control. An admin can stop the import at any time, and disconnecting clears the project from Meridian.

What's next

The registry tells Meridian which agents exist. Next, Meridian will match each Google agent to its Vertex AI spend from your detailed billing export, so the cost of an agent built on Google is attributed to that agent automatically.

After Google comes AWS. Our goal is simple: whichever cloud your agents run on, Meridian reads its registry, so every agent has an owner and a budget.

See it for your company

Start with an Agent Spend Assessment: connect your providers and your agent registries, and see what your AI agents cost, who owns them, and where the money goes.

Read the Google Agent Registry guide → · Start your assessment →

---

Google, Google Cloud and Vertex AI are trademarks of Google LLC. Microsoft and Agent 365 are trademarks of the Microsoft group of companies. Onaro is not affiliated with or endorsed by Google.