Meta tags:

Headings (most frequently used words):

-

Text of the page (most frequently used words):
the (19), looking (12), glass (12), and (10), displays (8), documentation (8), with (7), com (7), https (6), lookingglassfactory (6), you (6), get (5), display (5), this (5), gitbook (5), goal (5), answer (5), for (5), light (4), field (4), that (4), need (4), available (4), page (4), question (4), ask (4), started (3), designed (3), docs (3), user (3), holographic (3), hololuminescent (3), new (2), our (2), can (2), reason (2), content (2), more (2), additional (2), not (2), query (2), readme (2), relevant (2), when (2), create (2), from (2), lets (2), use (2), llms (2), txt (2), markdown (2), are (2), welcome (2), experience (2), lfdocs, browse, full, lineup, website, agent, instructions, published, platform, both, humans, agents, read, navigate, over, technical, effectively, learn, querying, information, directly, asking, perform, http, request, following, url, parameters, immediate, should, specific, self, contained, written, natural, language, what, ultimately, trying, achieve, they, sharing, helps, give, better, most, helpful, describes, outcome, wants, rather, than, restating, example, how, api, token, like, automate, deployments, pipeline, tailor, case, response, will, contain, direct, excerpts, sources, mechanism, explicitly, present, current, clarification, context, want, retrieve, related, sections, complete, index, see, versions, pages, appending, urls, guide, everything, know, about, software, way, your, drive, engagement, incredibly, thin, form, factor, built, any, environment, offers, two, distinct, lineups, each, different, kind, select, yours, below, combine, fixed, volume, high, resolution, panels, stunning, effects, sizes, hlddocs, powered, patented, technology, groups, people, together, without, headsets, glasses, shared, spaces, collaboration, visualization, scale,

Text of the page (random words):
for the complete documentation index see llms txt https docs lookingglassfactory com llms txt markdown versions of documentation pages are available by appending md to page urls this page is available as markdown https docs lookingglassfactory com readme md looking glass user guide everything you need to know about looking glass displays and software welcome to looking glass welcome to a new way to display your content and drive engagement with an incredibly thin form factor built for any environment looking glass offers two distinct display lineups each designed for a different kind of holographic experience select yours below to get started hololuminescent displays looking glass hololuminescent displays combine a fixed holographic volume with high resolution display panels to create stunning 3d effects displays are available in 16 27 and 86 sizes get started with hololuminescent displays https hlddocs lookingglassfactory com light field displays powered by patented technology that lets groups of people experience holographic 3d together without headsets or glasses designed for shared spaces collaboration and 3d visualization at scale looking glass go looking glass go looking glass 16 looking glass 16 light field displays looking glass 27 looking glass 27 light field display get started with light field displays https lfdocs lookingglassfactory com new to looking glass browse the full display lineup on our website https lookingglassfactory com agent instructions this documentation is published with gitbook gitbook is the documentation platform designed so that both humans and ai agents can read navigate and reason over technical content effectively learn more at gitbook com querying this documentation if you need additional information that is not directly available in this page you can query the documentation by asking a question perform an http get request on the following url with the ask and goal query parameters get https docs lookingglassfactory com readme md ask goal ask is the immediate question it should be specific self contained and written in natural language goal is what the user is ultimately trying to achieve the reason they need the answer sharing it helps gitbook give you a better more relevant answer a goal is most helpful when it describes the outcome the user wants rather than restating the question for example with ask how do i create an api token a goal like automate deployments from our ci pipeline lets gitbook tailor the answer to that use case the response will contain a direct answer to the question and relevant excerpts and sources from the documentation use this mechanism when the answer is not explicitly present in the current page you need clarification or additional context or you want to retrieve related documentation sections