Insights

AWS Agent Registry Now Feeds Onaro Meridian

By Brian Diamond

Published November 18, 2026

Last week, Microsoft Agent 365. On Monday, Google. Today, AWS.

Meridian now reads AWS Agent Registry, the catalog of agents your teams register on AWS. The agents in it come into Meridian, where finance can give each one an owner, a department and a budget.

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

Why this 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 on AWS run on model usage billed to your AWS account, and that bill doesn't say which agent spent it. Microsoft, Google and AWS each now keep a list of agents. None of them books the cost. Meridian is the layer that does: it attributes, controls and books what AI agents spend, across every provider.

How it works

  1. An admin connects an AWS account. In Meridian, under Settings, AWS Agent Registry, you enter the account and region. Meridian shows a read-only role to create in that account: a trust policy with an external ID unique to your company, and five read permissions. No AWS keys are stored in Meridian.
  2. Meridian checks the connection up front. One click confirms each link: the account, Meridian's own AWS identity, your read-only role, and the registry reads. Problems show up during setup, with a plain message, instead of failing quietly later.
  3. You preview before anything is written. Preview lists the agents Meridian found and the owner it would assign, and changes nothing.
  4. Your agents come into Meridian daily. Once a day, Meridian reads the registry and brings in new agents.
  5. Owners can come straight from AWS. Tag an agent's record with oasa-owner and the owner's email. If that email matches exactly one member of your Meridian organization, Meridian sets them as the owner. If it matches no one, Meridian keeps the email beside the agent so finance can follow up. An owner you assign in Meridian always wins.
  6. Finance takes it from there. Budgets, alerts, chargeback and journal entries to your general ledger work the same as for every other agent.

AWS Agent Registry support is in early access.

What's next

The registry tells Meridian which agents exist and who owns them. Next, Meridian will match each AWS agent to its Amazon Bedrock spend, so the cost of an agent built on AWS is attributed to that agent automatically.

And three clouds is a start, not a finish. Agents are also registered in Microsoft Entra, Salesforce, ServiceNow and more. Our goal hasn't changed: whichever platform your agents run on, Meridian reads its registry, so every agent has an owner, a budget and a line in the books.

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 AWS Agent Registry guide → · Start your assessment →


Amazon Web Services, AWS and Amazon Bedrock are trademarks of Amazon.com, Inc. or its affiliates. Google is a trademark of Google LLC. Microsoft and Agent 365 are trademarks of the Microsoft group of companies. Onaro is not affiliated with or endorsed by Amazon, Google or Microsoft.

Not sure which of your AI costs are being booked? Run the free Agent Spend Assessment.

Onaro Meridian is FinOps for agentic AI: the system of record that attributes, controls and books what AI agents spend.

Brian Diamond

Brian Diamond

Brian Diamond is a fractional Chief AI Officer and founder of Onaro. He has spent 30 years running infrastructure operations and founded LANStatus, a Connecticut managed services provider and Microsoft partner, in 2001. He holds a Chief AI Officer certification and writes the CAIO Brief on AI leadership for finance and operations.

LinkedIn · CAIO Brief · Author page

Markdown version