The paper trail

Small print.
Wide open.

A clear path from a claim to the page it came from. Here’s the filing, the research, and how we read it.

The documentS–1Anthropic, PBC26 OCT 2026 · 421 PP.
01The original SEC filingThe authoritative source, in your browser.SEC · HTML 02Download the saved filingThe complete 421-page document, optimized for downloading.PDF · 46 MB 03Download the full researchFindings, customer examples, calculations, and source references.Markdown

Page by page

Go straight to the source.

Page references count physical pages in the saved PDF, starting at 1. The printed filing number is shown separately when available.

Enter a page from 1 to 421. No PDF download needed.

From the filing

PDF page 40

Printed filing page 29 · Extracted page text

View on the SEC
Read the page text
Table of Contents

run to attempt to achieve the intended model improvements. We have in the past experienced, and may in the 
future experience, such failed or underperforming training runs, resulting in a loss of invested resources with 
limited or no corresponding benefit to our business. Given the scale of compute and other resources required 
for frontier model training and the extended timelines involved, a failed or underperforming training run could 
also  delay  our  product  roadmap,  affect  our  competitive  position,  and  adversely  affect  our  business,  financial 
condition, and results of operations.

In  addition,  new  models,  features,  or  capabilities  may  not  be  introduced  on  schedule,  may  not  perform  as 
intended,  may  require  significant  iteration  after  release,  may  fail  to  gain  meaningful  adoption,  or  may  take 
longer than expected to gain meaningful adoption, any of which could reduce customer demand or place us at a 
competitive disadvantage. In addition, considerations relating to model safety, interpretability, alignment, and 
welfare may lead us to limit or delay the deprecation of older models or to continue supporting legacy versions 
alongside  newer  releases,  creating  trade-offs  in  product  development  and  compute  distribution  that  could 
adversely  affect  innovation  velocity,  infrastructure  utilization,  and  revenue.  In  addition,  customers  who  have 
integrated  older  models  into  their  workflows  may  resist  migration  to  newer  versions,  and  any  accelerated  or 
forced deprecation could result in customer attrition, contractual disputes, or reputational harm. We have also 
changed, and may in the future change, usage limits, rate limits, or model and product capabilities, which could 
adversely affect our reputation and the perceived value of our offerings. Some of these changes have resulted, 
and  could  in  the  future  result,  in  claims  that  our  disclosures  regarding  model  access  or  capabilities  were 
inadequate or misleading.

Further,  the  industry  benchmarks  commonly  used  to  test  AI  models  may  not  accurately  reflect  real-world 
performance  or  utility,  and  even  models  that  perform  well  on  such  benchmarks  may  not  meet  customer 
expectations when deployed in production environments, which could lead to customer dissatisfaction, reduced 
usage,  or  reputational  harm.  If  we  are  unable  to  effectively  innovate  and  improve  our  models,  platform,  and 
applications  while  addressing  these  challenges,  or  if  competitors  are  able  to  deliver  AI  solutions  that  are 
perceived  as more  capable,  safer,  or  more  reliable,  or  that  offer  adequate  performance  at  a  lower  cost,  our 
business, financial condition, and results of operations could be adversely affected.

In addition, innovation in AI involves addressing complex and evolving challenges related to data quality, data 
integrity, training methodologies, bias, safety, accuracy, and the behavior of model outputs. AI algorithms may 
be  flawed,  and  AI  systems  may  contain  bugs,  errors,  or  defects  or  fail  to  follow  instructions  or  produce 
inaccurate, misleading, offensive, inappropriate, or otherwise harmful outputs; reflect or amplify unwanted or 
unknown  biases  present  in  training  data;  or  raise  concerns  relating  to  intellectual  property,  privacy,  or  other 
legal  and  ethical  considerations.  We  must  continually  invest  resources  to  identify,  mitigate,  remediate,  and 
reduce the occurrence of such issues, including through managing and improving datasets, training techniques, 
evaluation methods, safeguards, and human oversight. However, we may not be able to obtain the datasets that 
we need, including through licenses or strategic data partnerships. In addition, we or our data providers may 
use synthetic or AI-generated data in the training process, which could introduce quality issues, amplify biases 
or  errors,  contribute  to  model  degradation,  or  raise  novel  legal  questions  regarding  ownership,  licensing,  or 
intellectual property rights that may not be timely or clearly resolved by courts or regulators. Such unintended 
consequences, failures, or misuse of our models could impair customer trust, slow adoption, expose us to legal 
or regulatory scrutiny, or adversely affect our brand and reputation. 

If  we  are  unable  to  secure  adequate  compute  or  if  we  fail  to  direct  our  compute  effectively 
across our workloads, we may be unable to train models that remain competitive with those 
of our competitors or adequately serve our customers.

Our  ability  to  develop,  train,  improve,  and  deploy  frontier  models  depends  on  our  access  to  enormous  and 
increasing  quantities  of  specialized  compute.  The  training  of  Claude  models  has  required,  and  we  expect  will 
continue to require, substantial compute. Industry participants, academic researchers, and our own experience 
suggest  that,  in  certain  contexts,  applying  greater  amounts  of  compute  during  model  training  has  been 
associated with improvements in model capabilities. These observations are consistent with aspects of broader 
empirical  relationships  among  model  performance,  model  size,  training  data,  and  compute  scale  that  are 
commonly referred to as “Scaling Laws,” although the extent, efficiency, and durability of such improvements 
are  uncertain,  and  these  relationships  may  plateau,  diminish,  or  fail  to  materialize  at  larger  scales  or  under 
different  conditions.  Accordingly,  our  ability  to  remain  at  the  frontier  of  AI  capabilities  is  substantially 
dependent on our ability to secure compute at the scale required to sustain all our workloads, including to train 

29

Text is provided for reference. Check the original for tables, images, and exact formatting.

Find a section 16 starting points

Section links may begin before the exact paragraph cited in a finding. PDF numbers below use physical pages.

  1. Founders’ letterp. 3SEC
  2. Defined termsp. 12SEC
  3. Prospectus summaryp. 16SEC
  4. Risk factorsp. 38SEC
  5. Management’s discussion & analysisp. 144SEC
  6. Businessp. 190SEC
  7. Governancep. 254SEC
  8. Executive compensationp. 275SEC
  9. Related-person transactionsp. 293SEC
  10. Principal & selling stockholdersp. 299SEC
  11. Capital-stock rightsp. 303SEC
  12. Shares eligible for future salep. 318SEC
  13. Underwritingp. 327SEC
  14. Auditor change & expertsp. 345SEC
  15. Financial statements & notesp. 347SEC
  16. Part II & exhibit indexp. 413SEC

How this was made

Read in full.
Kept in context.

A snapshot of the filing dated , rather than a live record of later events.

3primary reviewers
421pages reviewed
43image instances checked

The review

Three primary reviewers read non-overlapping ranges of the complete main filing. All 43 embedded image instances were transcribed and visually reviewed, including the founders’ letter, charts, and customer case studies. Financial tables were also checked visually for dates, units, and column alignment.

A separate reviewer checked the draft’s calculations, accounting interpretations, and customer qualifications. An additional check covered the later merged findings. The result is 62 findings and 21 customer examples.

The boundary

Companion contracts and other exhibits named in the filing’s index are separate documents and were not independently reviewed. Customer outcomes, technical benchmarks, forecasts, and scientific priority claims remain attributed company or customer disclosures.

The numbers

Dollar figures are U.S. dollars. H1 means the six months ended June 30; Q2 means the three months ended June 30. The 2026 interim financial statements are unaudited. Our calculations show their inputs and are labeled separately from reported values.

Blank fields stay undisclosed. Figures with different periods, conditions, or potentially overlapping scopes are kept separate. An earlier tender price is not an IPO price.

What the evidence labels mean
Reported in filing
A company disclosure, with the period and accounting basis retained.
Company estimate / company claim
An estimate or assertion attributed to the company, with its uncertainty preserved.
Our calculation
A derived figure using cited inputs. It is not a separately reported company metric.
Customer example
A selected case study, with its measurement limits. It is not representative ROI.
Proposed / conditional
A status qualifier for an arrangement that is not yet effective or depends on stated conditions.

About updates. This edition is tied to the October 26, 2026 filing. Any later revision should identify its new source date and preserve the basis of earlier claims.

The footnotes are only the beginning.Explore the findings Read the story
The original, in context

Open the footnote.

A closer look at the filing

Anthropic · Form S-1PDF 1

Opening page 1…

Filed October 26, 2026. PDF is approximately 46 MB and opens only when requested. Section links may precede the exact cited paragraph.