Finding help and documentation

These docs live in three places, so you can reach the right answer from wherever you are: published on the web at docs.stackjack.io, one click away on any portal page, and readable by your AI assistant. This page maps all three.

Read the docs at docs.stackjack.io

The full product documentation is published at https://docs.stackjack.io, and it needs no account — prospects, teammates who have not signed in yet, and search engines can all read it. Selecting Documentation in the portal's left sidebar opens it in a new tab.

• The home page groups the docs into their sections — Getting Started, Connect Your AI, Connectors, Billing, and so on — as collections you can drill into.
• Search covers every published page.
• Each page has its own address of the form https://docs.stackjack.io/docs/<page>, so you can bookmark one or share it with a teammate.

Only the public documentation set is published there. Internal operator material is structurally absent — it is not filtered out at read time, it is never part of the published set at all.

StackJack staff have a second copy of these docs inside the portal, with extra staff-only sections. That browser is staff-only; everyone else reads docs.stackjack.io.

Get help for the page you're on (the "?" button)

On many portal pages a small Help for this page button (a question-mark icon) sits in the top header, next to the Support button. Selecting it opens the most relevant documentation article right there in a panel — no navigating away — with an Open full page link that opens that page on docs.stackjack.io in a new tab. The button only appears on pages that have a matching help article, so if you don't see it, that page has no dedicated help entry yet.

Don't confuse it with the neighboring Take a tour of this page button (also a round icon): that one replays the page's interactive walkthrough, while the Help button opens written documentation. See Portal navigation and roles for the full header rundown.

Ask your AI assistant

Because StackJack is an MCP gateway, your connected AI assistant can read these docs directly through two built-in platform tools:

• stackjack_search_docs — searches the documentation and returns a ranked list of matching pages (title, section, and a snippet).
• stackjack_get_doc_page — fetches a page's contents by its slug.

So you can simply ask, in whatever AI app you've connected: "Search the StackJack docs for how to connect Halo and summarize the steps." The assistant reads the same public documentation set published at docs.stackjack.io (operator pages are excluded). It reads it straight out of the running service, so an answer does not depend on the docs site being reachable.

Very large pages come back shortened. stackjack_get_doc_page caps a page body at 32,000 characters. A connector's full tool reference can be far larger than that, so those responses are cut, flagged as truncated, and carry a link to the whole page on docs.stackjack.io. If an answer looks like it stops mid-topic, ask the assistant whether the page was truncated and open the link. For a connector's complete per-tool detail, stackjack_get_tool_catalog is the better tool to ask for.

llms.txt for AI agents

For AI agents, StackJack follows the llms.txt convention: a machine-readable index of every public doc is served at https://mcp.stackjack.io/llms.txt, with a fuller variant (llms-full.txt) that inlines the page contents, plus a standard sitemap. Every entry links to that page's https://docs.stackjack.io/docs/<page> address. An agent pointed at StackJack can discover and read the entire public documentation set from that one file, no account needed.

Still stuck? Contact support

If the docs don't cover it, you can reach StackJack directly — see Getting help for the ways to open a ticket. Your AI assistant can even open a pre-filled one for you; see Support through your AI assistant.