Docs You Author
Like Code
Push Markdown in, pull the same Markdown back out, and drop live components straight into a doc body. No proprietary editor to fight, no export that mangles your tables, and no screenshot of a component going stale in a reference page.
Put a real component inside a doc
A doc body is not limited to prose. One line in your Markdown becomes a live component in the published page — the same component your marketing pages render, through the same path. A reference page can carry a working example instead of a picture of one that went stale six months ago.
# Pricing
Every plan includes the edge runtime.
:::component{slug=pricing-table version=1.2.0 props={"tier":"pro"}}
Annual billing saves two months.Markdown in, the same Markdown out
Four endpoints, two directions, two targets — docs and pages. Import creates a doc or replaces an existing one's body; export hands it back as clean Markdown with your component directives intact. Because the two are exact inverses, you can export a page, edit it in your own editor, and import it again without the content drifting.
Titles Stay Put
StableA leading heading is consumed as the doc title on import, and written back on export — so a file does not grow an extra heading every cycle.
Preview First
GatedReplacing an existing body can be run as a preview that returns a confirmation token and writes nothing, so a bulk import is inspectable before it lands.
Your source of truth can stay in git
If you would rather keep documentation in a repository than in an editor, you can. Author the Markdown where your code lives, review it in a pull request, and push it into the live manual — the same way this manual is maintained. The published page is the artifact, not the place you write.
Build an API reference from a spec
Point the OpenAPI importer at a spec — a URL or an uploaded file — and it generates a multi-page API reference: one page per tag, with multi-language code samples. When the API changes, re-run the import and the reference is current again. The importer is part of Docs Pro; on a plan without it the call is declined rather than half-completed.
# one spec file in, a full reference out
spideriq content docs:import-openapi \
--url https://api.example.com/openapi.json \
--section api-reference
# and any doc back out again, as Markdown
spideriq content markdown:export --doc <doc-id>Hand the whole loop to an agent
Create, edit, publish, import and convert are all available to AI agents over the SpiderIQ CLI and MCP — not a subset, and not a separate integration. An agent can read your existing Markdown, restructure a section, and publish it, because it is calling exactly the endpoints a person calls.