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 101

Printed filing page 90 · Extracted page text

View on the SEC
Read the page text
Table of Contents

customer  misconfiguration  or  misuse,  or  by  inadequate  access  controls  or  other  security  practices  by  our 
customers. Such incidents, even if caused by customer misconfigurations or misuse, or by a customer’s lack of 
adequate  security  controls,  may  impact  our  reputation  or  the  reputation  of  our  models,  platform,  and 
applications, and may subject us to liability exposure, disruption of commercial relationships, or other damage. 

Cyberattacks,  including  cyberattacks  directed  at  our  networks,  our  customers’  networks,  or  the  networks  of 
third  parties  with  which  we  have  relationships,  have  been,  and  may  in  the  future  continue  to  be,  amplified 
through  the  use  of  AI,  including  our  models,  platform,  and  applications.  Such  capabilities  may  be  used  to 
automate  or  scale  attacks,  impersonate  employees  or  members  of  senior  management,  or  otherwise  gain 
unauthorized access to our systems or those of our customers, partners, or vendors.

Failures  in  our  internal  systems  or  controls,  security  breaches,  failures  to  comply  with  our  privacy  or  data 
protection commitments, or other incidents, whether resulting from malicious activity, human error, or system 
limitations,  could  adversely  affect  our  reputation,  brand,  and  business  and  impair  our  ability  to  attract  and 
retain customers. Our offices and the data centers that host our infrastructure, many of which are operated by 
third  parties,  are  also  exposed  to  physical  threats  as  well  as  failures  by  the  operators  of  those  facilities.  A 
physical intrusion could damage equipment, interrupt our services, or provide a path to our systems and data, 
including our model weights, that bypasses our network defenses.

Although  we  have  dedicated  significant  resources  designed  to  identify  and  address  these  security  risks,  we 
cannot guarantee that our security measures will be effective or that our recovery protocols, backup, and other 
systems will be sufficient. Even where we detect an incident, our response may prove inadequate, including if 
we  misjudge  its  severity,  respond  too  slowly,  or  fail  to  fully  remediate  the  underlying  cause.  In  addition, 
incidents that appear minor when they occur may later prove significant when considered together with other 
incidents or with information learned afterward, and a series of related incidents, none of which is material on 
its own, could prove material in the aggregate. We continue to devote significant resources to protect against 
security breaches and other incidents, and we may need to devote significant resources in the future to mitigate 
and address problems caused by breaches and other incidents, which may divert resources from the growth and 
expansion of our business. 

Any actual or perceived security breach or other incident experienced by us or third parties with whom we do 
business, particularly our CSPs, could damage our reputation and brand, cause our business to suffer, require 
us to expend significant capital and other resources, cause us to incur increasing costs, including costs to deploy 
additional  personnel  and  protection  technologies,  train  employees,  and  engage  third-party  experts  and 
consultants, expose us to litigation or regulatory action, cause us to violate applicable privacy, data protection, 
security, and other laws and regulations, subject us to adverse publicity and a loss of confidence in our security 
measures, and cause us to incur significant fines, penalties, and other liability exposure, which could adversely 
affect our business, financial condition, and results of operations. We have taken steps to limit our liability for 
certain incidents, for example through warranty disclaimers and limitations of liability in our terms of service, 
but those contractual protections may not be upheld, or may not apply to certain claims, or may otherwise be 
insufficient to limit our liability exposure under applicable law.

In  the  EU,  we  face  increasingly  stringent  regulatory  reporting  obligations  for  cybersecurity  and  AI-related 
incidents. Under the GDPR, we must notify the competent regulators about incidents that involve personal data 
and  are  likely  to  result  in  a  risk  to  the  rights  and  freedoms  of  individuals.  Similarly,  the  EU  Network  and 
Information  Security  Directive  2022/2555  (“NIS2”)  requires  us  to  notify  the  competent  authorities  of  any 
significant  cybersecurity  incident  through  a  staged  process.  In  addition,  the  EU  AI  Act  requires  providers  of 
general-purpose AI models with systemic risk to keep track of, document, and report serious incidents without 
undue delay to the AI Office and competent authorities. Going forward, providers and deployers of high-risk AI 
systems,  as  defined  under  the  EU  AI  Act,  will  also  have  to  report  serious  incidents  or  malfunctions  without 
undue delay in certain circumstances.

In the United States, companies are increasingly subject to analogous incident reporting obligations, including 
under federal and state data breach notification laws, such as the New York Stop Hacks and Improve Electronic 
Data  Security  (SHIELD)  Act.  In  addition,  certain  U.S.  states  have  adopted  incident  reporting  laws  specific  to 
frontier model providers, such as the New York Responsible AI Safety and Education Act (RAISE Act) and the 
California Transparency in Frontier Artificial Intelligence Act. These frameworks create heightened compliance 
and liability exposure in case of delayed, incomplete, or inaccurate incident disclosures.

90

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.