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

The VA's $775.72M Ambient Scribe Award Is a Ceiling, Not a Commitment

ibl.ai EngineeringOctober 15, 2026
Premium

The VA's ambient scribe award is circulating as $775 million of committed AI spending. The contract record says something more useful to a buyer: it is a multiple-award IDIQ with a $775.72 million ceiling shared across every vendor eligible to compete for task orders, the contracts of record went to Knowtex and to Carahsoft rather than to the vendor named in most headlines, and the adoption figure everyone quotes is vendor-reported. Read carefully, it is an argument for holding your own measurement.

The Short Answer

The VA's ambient scribe award is a multiple-award IDIQ with a $775.72 million ceiling shared across every vendor eligible to compete for task orders, not $775.72 million committed to anyone. Its headline adoption figure is vendor-reported. That is the case for holding your own measurement: with ibl.ai you own all the code and the data, run it model-agnostic across any LLM, and pay with no per-seat pricing.

The widely-shared version of this award gets the figure right and the shape wrong. Correcting the shape changes what a buyer should take from it.

What exactly did the VA award in the $775.72M ambient scribe contract?

A five-year, multiple-award IDIQ for commercial cloud ambient clinical documentation, with two contract holders of record.

The VA's award is a multiple-award Indefinite Delivery, Indefinite Quantity contract carrying a total ceiling of $775.72 million over five years across all eligible competing vendors, reported on 22 September 2026.

It was awarded in September 2026 by the VA Technology Acquisition Center in New Jersey (36C10B) under solicitation 36C10B26R0006, with the award notice dated 22 September 2026.

The scope is the largest integrated health system in the United States. It delivers care to more than 9 million veterans across 1,380 healthcare facilities, including 170 VA Medical Centers and nearly 1,200 outpatient care sites.

The technology has to work in two electronic health record generations simultaneously: the legacy VistA/CPRS architecture and the new Federal EHR running on Oracle Health.

One detail in the award notice deserves more attention than it gets. The vehicle is for "Commercial-Off-The-Shelf (COTS), cloud-based" solutions and specifies a Software as a Service delivery model. The VA chose multi-tenant SaaS on purpose.

Who actually holds the VA ambient scribe contracts?

Knowtex Inc. and Carahsoft Technology Corporation, which is not the same list as the one in most headlines.

This is where the reporting and the contract record diverge, and it is worth being precise because the difference is instructive.

The award notice names the two contract holders as Knowtex Inc. and Carahsoft Technology Corporation. Carahsoft is a government aggregator and reseller, not an ambient scribe vendor.

Abridge's product reaches the vehicle through Carahsoft's contract. HIT Consultant's own account notes Abridge was selected "through a distribution partner," and headlines its award as winning a seat on the contract.

The asymmetry shows up in the vendors' own language. Only Knowtex claims "prime awardee," in a release dated 25 September 2026.

Both companies can compete for task orders. But if you are mapping a federal market, a vendor and its aggregator are different entities, and reading the vendor's press release as the contract record is how that distinction disappears.

Parameter What the award record says
Instrument Multiple-award IDIQ, not a single-vendor award
$775.72 million Total ceiling across all eligible competing vendors, over five years
Contract holders of record Knowtex Inc. and Carahsoft Technology Corporation (Abridge's federal reseller)
Money obligated to a vendor Determined later, per task order
Delivery model COTS, cloud-based, Software as a Service
EHR surface Legacy VistA/CPRS and Federal EHR (Oracle Health)

Does a $775.72 million IDIQ ceiling mean the VA committed $775.72 million?

No. An IDIQ ceiling is the maximum the government may spend under the vehicle, not an obligation to spend it, and here it is shared.

Nextgov's reporting states the ceiling covers "all vendors who are eligible to compete for task orders." The competition for the actual work happens after the award, task order by task order.

This distinction is not pedantry. It changes the arithmetic a vendor or an agency should run.

A headline reading "the VA committed $775M" implies a budget already allocated. What exists is permission to spend up to that figure across multiple vendors across five years, with each increment still to be competed.

For a buyer, the practical consequence is that winning a seat on the vehicle is the beginning of the sales cycle, not the end of it.

What did each ambient scribe awardee actually bring to the VA vehicle?

Two different profiles: an installed footprint across VA sites in one case, and clinical immersion plus a published evaluation method in the other.

A caveat first, because it is the kind of thing that gets asserted without a source. The VA has not published its source-selection rationale for 36C10B26R0006, and no outlet reports one. What follows is what each company brought, not a claim about why the VA chose them.

Abridge's stated advantage was integration reach. Per Nextgov on 14 September 2026, the company says its technology is "deployed at 70 VA sites and over 300 U.S. health systems." Other coverage renders this as more than 75 VA medical centers.

Running against two EHR generations at once is an integration achievement regardless of which figure you take.

Knowtex's route was domain immersion.

Founders Caroline Zhang and Jocelyn Kang met as Stanford freshmen studying AI and linguistics, founded the company in 2022, and spent a combined year in scrubs as medical scribes, working alongside clinicians by day and building at night.

They also published a clinical AI benchmark, KnowBench, on 15 September 2026, reporting that its own platform scores 97.99% on it.

Note the date: the week before the award notice. A self-published benchmark carrying a self-reported score is worth reading as a statement of method, not as independent validation, and it is too recent to have decided anything.

Is the VA's ambient scribe adoption data independent evidence?

Not strictly. The most-quoted figures in the story are reported by the vendors and relayed by the agency.

The numbers are genuinely impressive. More than 986,000 VA primary care appointments have used ambient scribes since October 2025, and veterans have declined the technology less than 1% of the time.

Read the attribution carefully. Nextgov's wording is that the appointment total comes "with vendors reporting veterans have declined the use of the technology less than 1% of the time" since October 2025.

Dr. Rebecca Gladding, acting deputy chief of psychiatry at VA Greater Los Angeles Healthcare System, is quoted on the under-1% figure. The agency relayed it; the vendors produced it.

This is not an accusation. The figure may be exactly right, and a sub-1% refusal rate across nearly a million appointments would be a real result.

But it is the single most persuasive number in a three-quarter-billion-dollar federal award, and the parties being evaluated are the parties who measured it. That is a governance gap, and no contract clause closes it.

Why does a buyer want the evaluation layer and audit trail under its own administration?

Because the artifacts are legal records, and because measurement supplied by the vendor being measured is weak evidence.

The governance requirements here are concrete.

Reporting on the award identifies three: mapping where data originates, setting access rules and consent protocols for sensitive patient conversations, and building auditability into the system as it scales.

The third one carries the weight. Once a generated note becomes part of a patient's legal health record, it has to be accurate and auditable, which turns "how was this produced" into a compliance question rather than an engineering curiosity.

To be clear about what this does and does not imply: the VA bought SaaS here deliberately, and a well-run multi-tenant service can absolutely provide audit logs and evaluation tooling. Vendors do.

The difference is who administers the instrument, who can change it, and what happens at contract exit. When the scoring and the trace run in a vendor's tenant, your evidence about the vendor depends on the vendor's continued cooperation.

This is the same structural point that governed the Pentagon's move from AI pilots to procurement-grade deployment: at procurement scale, control over the controls starts to matter.

On ibl.ai, that layer is part of the product you self-host. You run evaluations with model-graded scoring plus human annotation, keep transcripts and an audit trail of every query, and export the results, inside your own infrastructure.

What should a government or enterprise buyer do differently after the VA award?

Read the instrument before the headline, check who actually holds the contract, and ask who produced every number in the business case.

Three changes follow from the record above.

First, a multiple-award IDIQ with a $775.72 million shared ceiling is a different fact from $775.72 million awarded, and vendor marketing will not make the distinction for you.

Second, verify the awardee list against the award notice. Here the contract holders of record are Knowtex and a reseller, which is not what the headlines say.

Third, label every figure in your evaluation with its source. The VA's own flagship adoption statistic is vendor-reported, and that is in a federal award with far more procurement rigour than most private buyers apply.

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.

The Edge

A $775.72 million ceiling shared across competing vendors is permission to spend, not spending.

The contract holders of record are Knowtex and Carahsoft, a reseller, rather than the vendor most coverage names.

And the adoption statistic carrying the whole story, under 1% veteran refusal across 986,000+ appointments, was produced by the vendors and relayed by the agency.

None of that makes the award a bad one. It makes it a precise illustration of where procurement evidence actually comes from.

The reproducible lesson is that the numbers deciding an AI purchase tend to originate with the seller, and that generated clinical notes enter a patient's legal record, where accuracy and auditability are obligations rather than features.

Both pressures point the same way: toward measurement you administer. With ibl.ai you own all the code and the data, run it model-agnostic across any LLM, and pay with no per-seat pricing.

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.

Related Articles

AI Agent for Clinical Documentation: A Self-Hosted Scribe Hospitals Own

A self-hosted AI agent for clinical documentation drafts notes from the patient encounter while the hospital owns the model, the PHI, and the audit log. There's no per-provider SaaS fee and no protected health information leaving to a vendor under a BAA.

Blanca AmigotJune 9, 2026

A 9B Fine-Tune Beat Opus 4.5. Who Holds the Weights?

Coinbase post-trained Alibaba's open-weight Qwen3.5-9B on its own Onramp fraud data and reported beating Claude Opus 4.5 on all four metrics of its internal benchmark, with 55% lower serving latency and under $100 of training compute β€” and the more interesting half of the story is Part 2, where every newer frontier release scored worse than its predecessor on that same benchmark.

Mikel AmigotOctober 14, 2026

Can an Ontology Become Your Last System of Record?

A semantic layer becomes a system of record only when it originates state that exists nowhere else β€” and most never do, because they project over source systems that stay authoritative. This post gives four tests, one verified case where a semantic layer genuinely holds the record, two where it does not, and the custody question that outlasts the architecture.

Jaione AmigotOctober 14, 2026

Model-Agnostic Is Table Stakes. Source Code Isn't.

Microsoft Foundry has documented model-agnostic agents for months, and Microsoft even ships a disconnected on-premises agent path. Both are real, and neither is the thing enterprises should be buying on. The question a managed service still cannot answer is whether you receive the source code.

ibl.ai EngineeringSeptember 28, 2026

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

Most enterprise engagements are one-time, not subscriptions. You integrate ibl.ai with your own data, deploy it on your own infrastructure, and the engineering hours scale with the work β€” so the price tracks the scope, not your headcount.

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 Β· not a subscription

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