Reference

LLM-ready Documentation

Use Stacksona documentation with AI assistants, coding agents, and LLM-powered search without scraping noisy navigation or layout code.

What this site exposes

Stacksona docs include human-readable pages, public .md versions of every page, an llms.txt map, a full-documentation export, and copy buttons that package the current page for use in ChatGPT, Claude, Cursor, Copilot, or another coding assistant.

Asset	Path	Use
LLM map	`/llms.txt`	Curated links to the most important Stacksona docs and Markdown exports.
Full export	`/llms-full.txt`	One combined Markdown export for agents that need the entire docs context.
Public Markdown pages	`/integrations/n8n.md`	Append `.md` to a clean public page URL to return plain Markdown for agents.
Markdown archive	`/markdown/...`	Clean page content without navigation, layout, or script noise, kept as a generated archive.
Copy page for LLM	Button on every docs page	Copies a compact Markdown version of the current page.
Copy platform brief	Button on integration pages	Copies the current platform guide with usage context and first-call guidance.

Markdown URL pattern

For public docs pages, use the clean human URL for browsers and add .md for an agent-readable Markdown response.

Human URL	Markdown URL
`https://docs.stacksona.com/integrations/n8n`	`https://docs.stacksona.com/integrations/n8n.md`
`https://docs.stacksona.com/integrations/custom-rest`	`https://docs.stacksona.com/integrations/custom-rest.md`
`https://docs.stacksona.com/reference/api-contract`	`https://docs.stacksona.com/reference/api-contract.md`
`https://docs.stacksona.com/packages/mcp-server`	`https://docs.stacksona.com/packages/mcp-server.md`

Each HTML page also includes a rel="alternate" Markdown link in the page head so crawlers and agents can discover the plain-text version automatically.

How to use with an AI assistant

1
Open the platform page.
Choose n8n, Node, MCP, REST, or a platform recipe.
2
Click Copy page for LLM.
The copied text includes the page title, URL, description, key steps, tables, and code examples.
3
Paste into your coding assistant.
Ask it to adapt the Stacksona approval flow to your actual workflow, Gate URL, and sg_ agent key.

Do not paste real secrets into an LLM.

Use placeholders like STACKSONA_GATE_URL and STACKSONA_API_KEY. Hosted Gate URLs usually look like https://{gate-id}.stacksona.cloud, and the agent key starts with sg_.

Recommended prompt

prompt

Use this Stacksona documentation as the source of truth. Build an approval gate before the risky agent action. Use my own STACKSONA_GATE_URL and sg_ agent key as environment variables. Execute the action only when Stacksona returns allow or approved. Fail closed for rejected, pending, expired, blocked, invalid token, or API error states.

SEO and AI discovery assets

The site includes page titles, meta descriptions, canonical URLs, Open Graph metadata, structured data, a sitemap, robots file, Markdown exports, and LLM-focused discovery files. These help search engines and AI systems find the right Stacksona integration page for platform-specific approval questions.