ibl.ai Agentic AI Blog

Insights on building and deploying agentic AI systems. Our blog covers AI agent architectures, LLM infrastructure, MCP servers, enterprise deployment strategies, and real-world implementation guides. Whether you are a developer building AI agents, a CTO evaluating agentic platforms, or a technical leader driving AI adoption, you will find practical guidance here.

Topics We Cover

Featured Research and Reports

We analyze key research from leading institutions and labs including Google DeepMind, Anthropic, OpenAI, Meta AI, McKinsey, and the World Economic Forum. Our content includes detailed analysis of reports on AI agents, foundation models, and enterprise AI strategy.

For Technical Leaders

CTOs, engineering leads, and AI architects turn to our blog for guidance on agent orchestration, model evaluation, infrastructure planning, and building production-ready AI systems. We provide frameworks for responsible AI deployment that balance capability with safety and reliability.

Back to Blog

Government AI Agents: Build Once, Share Across Agencies

Miguel AmigotNovember 19, 2026
Premium

OMB's M-25-21 tells federal agencies to share and reuse AI code and models, yet agencies reported more than 3,600 AI use cases in 2025 and most of those with development details involve contractors. How an agency builds an AI agent once and lets other agencies copy it or call it, and the contract term that decides whether it can.

The Short Answer

Government agencies avoid rebuilding the same AI agent when one agency builds it once and the others either copy it into their own organization or call it over a standard interface, which is the reuse OMB's M-25-21 already asks for. On ibl.ai an agent copies across organizations and answers over an MCP endpoint, and you own all the code and the data, so a vendor contract is not what stands in the way.

Federal agencies reported more than 3,600 AI use cases in 2025, and the policy telling them to reuse rather than rebuild is already on the books. What can decide whether reuse happens is a clause in the contract that built the agent.

This post covers what the policy says, what stands in the way of reuse, and the two practical ways to share an AI agent between agencies.

What does OMB M-25-21 say about sharing AI code and models between agencies?

OMB Memorandum M-25-21, issued April 3, 2025, tells agencies to protect taxpayer dollars from duplicative spending and to reuse data, models, code and assessments of AI performance.

Its section on reuse goes further. Agencies must proactively share across the federal government their custom-developed AI code, including models and model weights, for AI applications in active use, whether the agency developed it or procured it.

The memo lists four exceptions: sharing is restricted by law, it creates an identifiable risk to security, privacy or the public, it creates a risk to agency operations, or the agency "is prevented from doing so by a contractual obligation."

It also asks a Chief AI Officer Council to promote shared templates, formats and technical resources. The direction is clear: build once, then reuse.

Why is AI agent reuse across government agencies hard to coordinate?

Government AI use is growing fast, which makes coordination harder. OMB's 2024 consolidated inventory listed 2,133 AI use cases from 41 agency submissions as of January 23, 2025.

A year later the count was far higher. Brookings' review of the 2025 inventories found 41 agencies documenting more than 3,600 use cases, 69% above 2024 and five times 2023.

Generative AI grew fastest. GAO counted generative AI use cases at 11 agencies rising from 32 in 2023 to 282 in 2024, roughly nine-fold, in GAO-25-107653.

The inventories show overlap even inside one agency. Brookings notes that some agencies listed the same tools multiple times for different offices, sometimes with different risk classifications.

GAO also records a structural limit: VA officials noted that existing privacy policy can prohibit information sharing with other agencies. Sharing an agent has to work without sharing the data behind it.

Who decides whether a government AI agent can be reused by another agency?

Often the contract does. Brookings found that around 63% of 2025 use cases with development details were developed by contractors, exclusively or with in-house resources.

By the time use cases reach full deployment, Brookings found, contracting is involved in 72% of them.

Put that next to M-25-21's exception for a contractual obligation. If the vendor keeps the source code, the model weights or the agent's configuration, the agency may have nothing it is permitted to hand to another agency.

That is why reuse is decided at signing, not after deployment. A contract that gives the agency the code and the data turns M-25-21's sharing requirement into something it can actually do.

The clauses that make ownership real are covered in Government AI Procurement Is Moving From Vendor Selection to Architecture Ownership. This post is about what an agency does with an agent once it owns one.

How can one government agency share an AI agent with another agency?

There are two practical patterns, and they suit different situations. The table compares them.

Question Copy the agent Call the agent over MCP
Where does it run? In the receiving agency's own organization Where the building agency runs it
Who maintains it? Each agency maintains its own copy One agency maintains one agent
Can it be adapted? Yes, to local rules, data and wording Only by the owning agency
Best fit Same problem, different data or policy Same problem, same answer for everyone
On ibl.ai Cross-organization agent copy from the auth app The agent-chat MCP endpoint runs a full agent turn

Copying fits when two agencies face the same problem under different rules, such as two benefits programs with different eligibility criteria. The second agency starts from a working agent instead of a blank page.

Calling fits when the answer should be the same everywhere, such as one authoritative agent on a shared regulation. Every agency gets the same answer, and a correction is made once.

How does ibl.ai let agencies copy and call each other's AI agents?

ibl.ai shipped both patterns in the week of November 6 to 13, 2026, as recorded in the platform update for November 13, 2026.

Copy. An agent can be copied into another organization from the auth app, and the organization list is searchable. For a government deployment, each agency or program can be its own organization on one platform.

Call. The agent-chat MCP tool is reachable at /mcp/agent-chat/<agent_id>/, so it works as a custom connector in Claude Desktop or claude.ai with only an Authorization header.

Each MCP call runs a full agent turn, using the agent's system prompt, tools, trained documents and memory, and passes moderation, spend caps and credits. An optional session id lets a client continue the conversation.

Because the platform is model-agnostic, a shared agent is not tied to one model vendor. The agency that copies an agent can run it on a different LLM than the agency that built it.

What should an agency check before it shares an AI agent with another agency?

Start with the four M-25-21 exceptions, because they are the real limits. Confirm that no law, security or privacy risk, operational risk or contract term prevents the sharing.

Then separate the agent from its data. The VA privacy concern GAO recorded, that existing privacy policy can prohibit sharing with other agencies, is a reminder that an agent's instructions and tools can travel while the records behind it stay home.

Finally, choose copy or call deliberately. Thousands of reported use cases leave plenty of room for both: copy where rules differ, call where one answer should hold everywhere.

ibl.ai is family-owned and operated from New York, NY, a U.S.-headquartered, domestically-owned long-term partner for agencies that want to own their agents. More on deployments for public-sector buyers is on the government solutions page.

Why does owning the AI stack matter?

ibl.ai is the agentic AI platform where you own all the code and the data. You self-host the entire stack inside your own perimeter, run it model-agnostic across any LLM and switch anytime, and pay by usage with no per-seat pricing β€” so you can deploy anywhere: your cloud, on-premise, GovCloud, or fully air-gapped.

  • You own all the code and the data

    Full source code under a perpetual license, running on your infrastructure. Not API access to someone else's platform β€” the stack itself is yours.

  • Model-agnostic

    Run any LLM β€” Claude, GPT, Gemini, Llama, Command, or your own fine-tune β€” and switch providers without rewriting the platform.

  • No per-seat pricing

    Usage-based billing against a budget cap you set. Cost tracks what your organization actually uses, not how many people you employ.

  • Deploy anywhere

    Your cloud, your VPC, on-premise, GovCloud, or a fully air-gapped network with no outbound connectivity.

1.6M+ users across 400+ organizations run the platform this way, including NVIDIA, MIT, and Syracuse University.

ibl.ai is family-owned and operated from New York, NY β€” a U.S.-headquartered, domestically-owned long-term partner, not a vendor that sells licenses and moves on.

See the ibl.ai AI Operating System in Action

Discover how leading universities and organizations are transforming education with the ibl.ai AI Operating System. Explore real-world implementations from Harvard, MIT, Stanford, and users from 400+ institutions worldwide.

View Case Studies
Work with our team

Pilots, deployment, and full ownership

Every engagement is scoped to the work: you integrate ibl.ai with your own data, deploy it on your own infrastructure, and the engineering hours scale with the scope β€” so the price tracks the scope, not your headcount. Most customers keep us on afterwards for platform updates, new agents and integrations, and ongoing services.

Start here

Pilot

from $15K

fixed scope Β· fixed timeline

A time-boxed proof of value on your real data β€” not a slide deck.

Best for: Teams that want to see ibl.ai working before committing.

  • Deployed on your infrastructure or our cloud
  • 1–2 production agents wired to a slice of your data
  • One integration (LMS / SIS / SSO / data source)
  • Weekly working sessions with our engineers
  • Pilot fee credits toward a full engagement
Scope a pilot
Most common

Integration & Deployment

$25K – $80K

one-time fee Β· scoped to the work

Full deployment integrated with your data and systems. Engineering hours scale with scope.

Best for: Organizations rolling ibl.ai out across a department, campus, or business unit.

  • Platform deployed in your VPC, on-prem, or air-gapped
  • Integrated with your data + identity (SSO / SAML)
  • Multiple custom agents built to your workflows
  • Engineering hours proportional to scope
  • You own the data Β· run any LLM you choose
Plan a deployment
Full ownership

Codebase Transfer + Custom AI Engineering

Custom quote

perpetual license Β· you own the stack

We transfer the full source code. You own and self-host the entire platform β€” outright.

Best for: Organizations and enterprises that benefit from perpetual ownership and sovereignty.

  • Complete source-code transfer + perpetual license
  • Dedicated AI engineering team on your roadmap
  • Custom agents, models, and integrations to spec
  • Air-gapped capable Β· zero vendor lock-in
  • Family-owned, New York–based long-term partner
Talk about ownership
You own the code and data Run any LLM β€” Claude, GPT, Gemini, Llama Family-owned & operated from New York, NY