A rich block editor — callouts, embeds, tabs, live endpoint references — attached to the sheets, scripts, and connections it describes. Then publish the whole thing as a branded doc site, with per-script API references generated for you.
wiki links resolve to real sheets, contracts & scripts
Write in rich blocks next to the data, then ship a whole doc site — without leaving PrysmOS.
A rich editor with callouts in every tone, embeds, tabs, accordions, and API Endpoint blocks that render live endpoint references — attached to the thing it describes.
Live co-editing keeps the whole team on the same page — literally. Markdown files import straight in; versions, reactions, and images come standard.
Turn a collection into a public portal: categories, your theme, your domain, site-wide visibility controls. Token-gated links share individual docs without going public.
Publish a script and PrysmOS generates its endpoint reference — rendered publicly on your doc site, always in sync with the code.
Internal docs and public doc sites share one editor — so the page you write for your team can ship to customers unchanged.
Callouts with tones, embeds, tabs, accordions — pages that explain, not walls of plain text.
Drop an endpoint block into any doc and it renders a live reference — method, route, params — straight from the published script.
Docs attach to the exact sheet, script, or connection they describe — with wiki-links that resolve to the real thing.
The whole team in the same doc at the same time — cursors, edits, and no 'who has the latest version?' ever again.
Every save is a version. Diff what changed, see who changed it, roll back to any draft in one click.
Lightweight reactions on every page — see which runbooks people rely on and which ones quietly rot.
Drop screenshots, diagrams, and charts straight into the doc. They're hosted with it — no broken links.
Bring your existing docs with you — .md files import cleanly, structure intact, ready for blocks and co-editing.
Any collection becomes a public portal — categories, themes, site visibility, your logo, your domain. Updating the docs updates the site.
Share a single unpublished doc — or a whole private site — with a token link. Rotate or revoke it anytime; access dies instantly.
Every published script gets a reference page generated from its code — routes, request shape, auth — rendered publicly and always current.
Organize pages into categories, pick a theme, control site visibility per site. A docs portal that looks like yours, not ours.
Browse the categories, search the pages, then ask a question — answers come from the published docs and cite their source.
The refunds_ok contract re-verifies refunded rows within the hour.
Ask AI · answers from these docs only
The refund runbook sits next to the payments sheet and the refunds_ok contract. When a violation wakes someone at 3am, the doc they need is already open in the same tab.
Publish your endpoint collection as a dev-reference site — auto-generated per-script references, your theme, your domain. The 'how do I auth?' page writes itself.
Ship a customer-facing portal from the docs you already maintain. Token-gated links handle beta docs and partner-only pages without a second system.
Any collection of docs can be published as a public portal — pick a theme, organize pages into categories, control site visibility, and it's live on your own domain. Updating the docs updates the site; there's nothing to rebuild.
Write once, publish as a site, let the AI front desk handle repeat questions. Free to start — no credit card required.