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

Palantir's $4.9M IRS AI Agent Order, Read Line by Line

Miguel AmigotNovember 19, 2026
Premium

The reported $5M Treasury AI contract is a $4.9M IRS order to Palantir for an AI correspondence agent for Schedule C, placed on a Palantir-only purchase agreement. What the public record shows, what it does not, and the ownership questions an agency should settle before ordering an AI agent.

The Short Answer

The "$5 million Treasury AI contract" is a $4,899,521.50 IRS order to Palantir, signed November 5, 2026, to build an AI correspondence agent for IRS Schedule C over four months. It is a call on a Palantir-only IRS purchase agreement, not a new contract. The question it raises applies to every agency buying agents: on ibl.ai you own all the code and the data.

The headline came from a social post. This piece reads the federal spending record instead, because the record answers what the headline cannot: what was bought, how, for how long, and what the agency will hold when the order ends.

What did the IRS actually buy from Palantir in November 2026?

The IRS bought an AI agent to handle correspondence for Schedule C, the form on which, per the IRS, a sole proprietor reports income or loss from a business they operated.

The USAspending award record describes the work as the design, development and deployment of AI-based assistants, agentic AI capabilities, workflow integrations and semantic ontology governance "to build an AI correspondence agent for the IRS Schedule C."

The order is 205AE927F00003. The IRS IT Operations office both awarded and funded it, and the record files it under the IRS major program "Compliance Hub" with product code DA10, application development software as a service.

Field in the federal record Palantir IRS order 205AE927F00003
Awarding bureau Internal Revenue Service (Department of the Treasury), IT Operations
Signed November 5, 2026
Period of performance November 6, 2026 to March 5, 2027
Amount obligated $4,899,521.50
Award type BPA call on IRS BPA 205AE926A00004
Parent vehicle of the BPA GSA Multiple Award Schedule contract 47QTCA24D004L
Work AI correspondence agent for IRS Schedule C

Is the Palantir IRS award a $5 million contract or a ceiling?

The Palantir IRS figure is money obligated, not a ceiling, and it is not a standalone contract. USAspending reports $4,899,521.50 obligated, equal to the base and exercised options, and lists no larger options value for the order.

It is a call on IRS blanket purchase agreement 205AE926A00004, described as the "Compliance Hub - Compliance Vertical Federal Platform" BPA. That agreement was signed September 29, 2026 and runs to September 29, 2030.

The BPA is recorded as a single award, with one offer received, placed against Palantir's GSA Multiple Award Schedule contract.

The BPA itself shows $0 obligated and a potential value of $250 million, including all options. Money moves only through calls like this one, so the agreement is the channel and each call is a purchase.

How does the Schedule C agent fit Palantir's other IRS work in 2026?

The Schedule C agent is the latest of five Palantir orders the IRS placed in about six weeks. A USAspending search of Palantir's Treasury awards lists them, and together they come to about $53.1 million obligated.

Start date IRS order (as described on USAspending) Obligated
Sep 23, 2026 Compliance Hub IRS case selection: software licenses plus operations and maintenance $21,707,685
Sep 24, 2026 Case management task order $6,114,198
Sep 28, 2026 Lead and case analytics support services $11,380,366
Sep 29, 2026 Compliance Hub compliance vertical federal platform, task order 1 $9,002,423
Nov 6, 2026 AI correspondence agent for Schedule C $4,899,522

Read together, the orders show the pattern that matters. The agent is not the only purchase: the IRS also buys software licences, case selection, case management and analytics from Palantir under separate orders.

That is a normal way to buy, and often a sensible one. It also means the ownership question is best settled across the orders, not one order at a time.

Who owns an AI agent an agency buys as a task order?

Who owns an agency's AI agent is set by the order's terms, and the public spending record does not show them. USAspending reports amounts, dates and descriptions, not data-rights clauses, so this record cannot say who owns the agent's code, prompts or ontology.

Federal policy says where to look. OMB memo M-25-22, issued April 3, 2025, lists lock-in protections that include knowledge transfer, data and model portability, and "rights to code and models produced in performance of a contract".

That term covers what a contractor builds under the order.

A commercial platform licensed underneath the agent, and the product code here is software as a service, is a separate licensing question. We worked through that gap in government AI procurement moving to architecture ownership.

What should an agency ask before ordering an AI correspondence agent?

An agency ordering an AI correspondence agent should settle five things before signing, because a four-month order like the IRS one ends long before the agent stops mattering. Each question maps to an M-25-22 protection.

  1. Code. Does the agency receive the agent's code, prompts and workflow definitions, or only the right to use them while the order runs?
  2. Ontology. Who owns the semantic model the agent reasons over, and can it be exported in a form another system reads?
  3. Data and derived assets. Do drafted replies, review decisions and evaluation sets stay with the agency at closeout?
  4. Model. Can the agency change the underlying LLM without rebuilding the agent?
  5. Platform. If the platform licence lapses, does the agent still run?

None of these questions implies a vendor answers them badly. They are the terms an agency needs in writing either way, and the ones M-25-22 tells agencies to address in the solicitation and contract terms.

How does ibl.ai approach the same agency AI agent?

ibl.ai builds the same kind of agent on a stack the agency keeps. You own all the code and the data, the agent runs model-agnostic across any LLM, and it deploys anywhere: your cloud, GovCloud, on-premise or fully air-gapped.

Source code comes with the Codebase Transfer engagement.

The pieces map to the IRS order's own description.

Agentic OS runs the AI agents and their workflow integrations, and Agentic Ontology is an MIT-licensed knowledge layer that serves an agency's systems to agents inside its own network. The Palantir Ontology comparison covers that layer in depth.

ibl.ai does not claim a FedRAMP authorization; the stack runs inside an environment the agency controls and authorizes.

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. More for agencies is on ibl.ai for government.

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

Super Intelligence Force: What Changes for Agencies Buying AI

President Trump announced the Super Intelligence Force on 4 October 2026, a task force chaired by DNI Jay Clayton with 120 days to report on AI's risks and opportunities. Its reported charter covers AI threats and recommendations, not contracting; agencies still buy AI chiefly under OMB M-25-22, whose terms already reward data rights, portability and code an agency can keep.

ibl.ai EngineeringOctober 9, 2026

Government AI Procurement Is Moving From Vendor Selection to Architecture Ownership

OMB's M-25-22 asks AI contracts for data portability, lock-in protection and rights to code produced under the contract, and GAO found a contractor charging an agency to get its own data back. What architecture ownership adds, layer by layer, and the contract clauses that make it real.

ibl.ai EngineeringNovember 9, 2026

Sovereign AI Is Now Procurement Policy, Not Rhetoric

France's Ministry of the Armed Forces signed a framework agreement with Mistral in January 2026, and Nigeria's National Digital Cloud Policy scopes sovereignty to government and regulated data. Sovereign AI has moved from speeches into contracts β€” and the contract terms are where it succeeds or fails.

Jaione AmigotAugust 24, 2026

Sovereign AI for Federal Agencies: Why Early Access to Vendor Models Isn't a Security Strategy

Federal agencies are accepting 'early access' to commercial AI models as a security posture. It isn't. Here's what sovereign AI actually looks like.

Blanca AmigotMay 9, 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

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