> For the complete documentation index, see [llms.txt](https://docs.42.space/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.42.space/readme.md). # Welcome to 42 Holla, welcome to 42 — a novel asset-issuance protocol where event outcomes trade as liquid tokens with defined settlement rules. Here, you'll find everything you need to get started on 42. ### Jump right in

		Cover image
Introduction to 42	Learn what 42 Markets is, what it does, and where it fits in the broader ecosystem.	Group 48095906.png	Introduction
App Guide	Step‑by‑step walkthrough of the 42 platform so you can trade and navigate the platform with confidence.	Group 48095905.png	App Guide
Protocol Mechanics 101	Dive into the core architecture and advanced concepts behind 42.	Group 48095904.png	Protocol Mechanics 101

--- # 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.42.space/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.

:bolt:

:tablet-button:

:robot: