Meta tags:

Headings (most frequently used words):

-

Text of the page (most frequently used words):
the (18), your (11), and (10), document (10), research (9), documentation (8), search (8), account (8), information (7), you (6), with (6), personalised (6), help (5), ulii (5), this (5), finding (5), gitbook (5), goal (5), answer (5), page (4), get (4), question (4), ask (4), for (3), https (3), org (3), available (3), find (3), documents (3), content (3), legislation (3), create (3), additional (3), that (3), need (3), llms (2), txt (2), markdown (2), readme (2), getting (2), started (2), legal (2), helps (2), navigate (2), courts (2), inside (2), working (2), table (2), contents (2), advanced (2), subject (2), area (2), tags (2), similar (2), saving (2), commenting (2), alerts (2), follow (2), topics (2), interest (2), reset (2), password (2), delete (2), support (2), can (2), reason (2), more (2), not (2), query (2), user (2), relevant (2), when (2), from (2), use (2), complete, index, see, versions, pages, are, appending, urls, share, quickly, confidence, start, judgments, toc, improve, results, understanding, personalise, overview, creating, resources, agent, instructions, published, platform, designed, both, humans, agents, read, over, technical, effectively, learn, com, querying, directly, asking, perform, http, request, following, url, parameters, immediate, should, specific, self, contained, written, natural, language, what, ultimately, trying, achieve, they, sharing, give, better, most, helpful, describes, outcome, wants, rather, than, restating, example, how, api, token, like, automate, deployments, our, pipeline, lets, tailor, case, response, will, contain, direct, excerpts, sources, mechanism, explicitly, present, current, clarification, context, want, retrieve, related, sections,

Text of the page (random words):
for the complete documentation index see llms txt https help ulii org llms txt markdown versions of documentation pages are available by appending md to page urls this page is available as markdown https help ulii org readme md getting started find research and share legal information on ulii ulii helps you quickly find legal information and navigate documents with confidence start your research search content finding information search for content md find legislation legislation finding legislation md courts judgments courts md search inside a document working with a document search inside a document md document table of contents working with a document document table of contents toc md improve your results advanced search finding information advanced search md subject area tags finding information understanding subject area tags md similar documents finding information similar documents md personalise your research personalised research overview personalised research getting started md saving a document personalised research saving a document md commenting in a document personalised research commenting in a document md search alerts personalised research creating search alerts md follow topics of interest personalised research follow topics of interest md your account create an account your account create an account md reset your password your account reset your password md delete your account your account delete your account md get help and support additional resources get help and support md 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 help ulii org 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