Policy & Regulation

OPM buys $1 million in Anthropic software via Carahsoft

GSA awarded Carahsoft a $1 million Anthropic software order funded by OPM on November 16, 2026. The record omits the Claude product, seats, workload and any OneGov discount.

OPM’s IT Office Funds Anthropic Software Order Through Carahsoft
OPM’s IT Office Funds Anthropic Software Order Through CarahsoftStartupStockPhotos / pixabay
By Marcus Bennett6 min read

Why it matters

  • GSA awarded Carahsoft a $1 million Anthropic software delivery order on November 16, 2026, funded by OPM's Office of the Chief Information Officer.
  • The firm-fixed-price order runs through November 15, 2027, but does not identify the Claude product, seat count or intended workload.
  • The full-and-open competition received one offer and used no set-aside.
  • GSA's OneGov page lists a 40% discount on consumption-based token usage through January 31, 2029, but the OPM award does not state whether it applied.
  • Anthropic reported approximately 500 government organizations using Claude on October 27, 2026, with weekly Claude for Government activity up about eightfold since February 2026.

By Marcus Bennett

The General Services Administration (GSA) awarded Carahsoft Technology Corp. a $1 million delivery order for Anthropic software on November 16, 2026, according to a Federal Procurement Data System record.

The funding source was the Office of Personnel Management’s Office of the Chief Information Officer, according to the procurement record. The firm-fixed-price order runs through November 15, 2027, covering a defined performance period. The record classifies the work as business-application and application-development software as a service, and names Carahsoft, rather than Anthropic, as the awardee.

The adoption context is broader than the purchase alone. Anthropic reported on October 27, 2026 that approximately 500 U.S. federal, state and local government organizations used Claude.

Two company-reported growth rates sharpen that scale. Weekly Claude for Government active users had risen about eightfold since February 2026, while usage across federal civilian agencies had grown about 20-fold over the preceding year.

The pricing context is less certain. GSA’s OneGov IT page lists a Claude models and API agreement with a 40% discount on consumption-based token usage through January 31, 2029. The OPM award itself does not mention OneGov or state a discount.

The Federal Procurement Data System structure separates the agency’s funded purchase from the technology supplier by naming Carahsoft as awardee and Anthropic as the requirement. For Anthropic, the order creates a concrete federal purchase; for Carahsoft, it turns scheduled access to government software into a funded delivery obligation.

What exactly did OPM order?

The public description identifies only the requirement “Anthropic.” It does not identify:

  • Which offering OPM is buying: Claude for Government, Claude Enterprise or the Claude API.
  • A seat count or number of users.
  • An intended workload.

The deployment details remain undisclosed. The financial commitment and performance period are therefore clearer than the scope of the deployment. The source supplies no seat count, intended workload or product selection, leaving three materially different government offerings under one $1 million order.

That limitation matters because the record cannot show which authorization level, user scale or usage model OPM selected. The public procurement data identifies a vendor and a price, not the software configuration needed to assess either.

What did the competition produce?

The order used Carahsoft’s GSA Multiple Award Schedule and procedures for commercial products and services, according to the procurement record. The process therefore moved through an established federal contracting channel rather than a newly negotiated vendor agreement.

The record labels the procurement “full and open competition” under multiple-award fair-opportunity procedures. It also reports “one offer received” and no set-aside used.

For buyers and sellers, that combination narrows what the competition label proves: the file documents a formally open process, but not a multi-offer price test. No competing bid appears in the record, leaving the $1 million firm-fixed-price amount without a disclosed comparator.

The market implication is structural rather than competitive. Carahsoft sits between GSA’s contracting framework and the agency’s need, while Anthropic remains the named technology supplier. That arrangement lets a reseller execute the transaction without requiring the software company to appear as the awardee.

How does OneGov fit into the order?

Carahsoft announced on October 30, 2026 that OneGov access to Claude had become “transactable” through its Multiple Award Schedule. Its announcement covered Claude for Government, Claude Enterprise and the Claude API, establishing a procurement route for each product category discussed alongside the order.

The delivery order itself does not mention OneGov or state a discount. It therefore does not establish that the schedule’s pricing terms governed OPM’s purchase, even though Carahsoft had announced OneGov availability earlier.

GSA’s OneGov IT page lists a Claude models and API agreement with a 40% discount on consumption-based token usage through January 31, 2029. The agreement carries no commitment or minimum order and provides access through Anthropic, resellers and supported cloud marketplaces.

According to GSA, OneGov supplies pre-negotiated pricing and standardized terms, but individual agencies still have to obtain quotes, document fair opportunity and meet agency-specific thresholds when ordering. That division makes the program a common commercial framework, not a replacement for an agency’s procurement decision.

The award and GSA’s OneGov page together establish two different levels of detail. The OPM order commits $1 million and a performance window. The OneGov agreement establishes program pricing and access routes, while leaving the agency’s funded scope and duration to the order.

That is the practical limit of the public price data.

The procurement record supports a dollar commitment and a delivery window. It does not support a per-seat or per-token calculation.

How are government agencies using Claude?

Anthropic’s October 27 report describes agencies using Claude to manage backlogs, handle records and forms, and modernize old code. Those examples place the technology across administrative workflow and software maintenance rather than limiting the government push to a single use case.

Anthropic’s three measures count different things: organizations using Claude, weekly active users of Claude for Government, and usage across federal civilian agencies. The report supplies growth multiples but no baseline totals, so the eightfold and 20-fold increases do not reveal absolute active-user or usage totals from this source.

The OPM order adds a named agency purchase to that reported adoption base. Anthropic’s figures indicate a widening government user presence, while the procurement record shows the commercial path for converting that presence into contract revenue.

Which security status could apply?

The unresolved product choice carries compliance consequences because the October 2026 announcements assigned different authorization statuses to the government offerings.

Claude for Government operates at the Federal Risk and Authorization Management Program (FedRAMP) High authorization level and is intended for sensitive unclassified work. Claude Enterprise was in process for FedRAMP Moderate authorization through FedRAMP 20x when those announcements appeared.

Because the public OPM description names neither offering, it does not establish which authorization status governed the order. The source also gives no FedRAMP status for the Claude API. Resolving that gap requires a product identification the award record does not provide.

That uncertainty does not erase the purchase. The record still establishes a $1 million order funded by OPM through November 15, 2027 and places Carahsoft in the transaction with Anthropic as the named requirement.

Who controls price and deployment scope?

The arrangement captures the operating model of government AI procurement: pre-negotiated agreements can standardize access and pricing, agencies still determine funded scope and duration, and resellers can execute the transaction.

Anthropic’s and Carahsoft’s disclosures show the stakes from each side. For Anthropic, the October adoption numbers and November order show why federal demand matters. For OPM, the unresolved product choice leaves procurement, security and cost questions open.

What would clarify the purchase?

The next verifiable milestone would be an OPM or GSA disclosure naming the Claude offering, user count or workload, and whether the 40% OneGov discount applied. Those details would connect a $1 million award to a measurable deployment rather than an unidentified software purchase.

Until then, the November 16, 2026 record proves that OPM committed $1 million through Carahsoft’s government schedule for a term ending November 15, 2027. It does not reveal the product, user scale, workload or discount-adjusted value of Anthropic’s federal foothold.

Source: unite.ai

Share this article:

More from Marcus Bennett

Marcus Bennett

Show full bio

Senior reporter covering companies, deals and strategy in artificial intelligence and machine learning at AI In Context.

718 articles

Related articles

  1. Anthropic gives startups a free year of Claude Team and $1,000 in API credits
  2. Anthropic’s IPO filing reveals its enterprise lock-in strategy
  3. Anthropic opens Claude to civilian US agencies while Pentagon fight drags on
  4. Anthropic expands Claude Startups program with up to $45,000 in credits
  5. Anthropic's Q3 Revenue Hits $16.8 Billion Ahead of IPO

« Previous articleNext article »