Read docs with an agent

Read public documentation without signing in#

Every documentation page is server-rendered HTML. Its article, headings, links, and examples are available without JavaScript or an account. Use View Markdown on any page for the same content as plain Markdown.

The Markdown export, search index, and consolidated guide are generated from the same article templates as the human-facing pages.

• /llms.txt: concise discovery index with HTML and Markdown links.
• /llms-full.txt: complete documentation corpus for retrieval.
• ChatGPT workspace Markdown: connection, calculators, prompt examples, project review, and limits.
• Documentation search index: page and section text with navigable URLs.
• /sitemap.xml and /robots.txt: public-page discovery and crawl policy.

curl -fsS https://ventilatepro.com/exam/cli/chatgpt.md
curl -fsS https://ventilatepro.com/llms-full.txt

If an HTTP client receives an edge challenge or a 403 response, report the URL and status to support. An access-policy declaration alone does not prove that a particular client can fetch the site.

Discover the connected server's tools#

Documentation explains workflows; the connected server's tools/list schemas define callable tools and arguments. Registry name: com.ventilatepro/ventilatepro.

• The ChatGPT sidebar workspace uses https://ventilatepro.com/mcp/workspace with projects:read, entities:read, and calc:read. Its calculator and saved-result tools are read-only.
• The wider MCP integration uses https://ventilatepro.com/mcp remotely or ventilatepro-mcp locally. Discover current capabilities with vp_describe_capabilities.
• Local calculator tools run without authentication. Remote MCP connections require OAuth, including for calculator calls.
• For project tools, verify identity, scopes, and membership. Resolve record IDs through accessible lists and inspect all relevant pages.

Follow tool discovery and the API contract before constructing automation. The public documentation does not grant access to private project records.

Keep engineering answers traceable#

Report the inputs, units, formula or basis, source records, and calculation freshness. Check isError and structured errors before treating a tool response as engineering data. Use the connected schema for specialized guarded writes and obtain authorization for the intended operation.

Public documentation may be crawled, indexed, quoted with attribution, and used for retrieval. Public documentation access is independent of private project access.

Product references: feature catalog, changelog, and support.