Thoth is markdown extended for scale: readable cold, composable across files, structured enough for robots to read and write, and with tooling for humans and robots alike.
Stay up to date on our progress and key decisions. No spam, and we won't share your email. Powered by Buttondown.
# Authentication Guide ## Setup {./shared/api-keys.md#install} ## Endpoints {#endpoints} {{./endpoints.csv | as:table}} Need higher limits? See {#endpoints} or contact support.
API keys live in your dashboard. Each request requires the key in the Authorization header as a bearer token.
| Method | Path | Description |
|---|---|---|
| GET | /users | List users in the workspace. |
| POST | /sessions | Begin a new authenticated session. |
| DELETE | /sessions/:id | Revoke an active session. |
Need higher limits? See Endpoints or contact support.
Markdown won because it stayed out of the way. The source was the document — no renderer, no chrome, no ceremony. Thoth keeps that instinct, and builds on it.
What we're asking markdown to do has grown. The same format now carries our knowledge bases, our technical specs, the context we hand to language models, the writing that used to live in heavier tools. Thoth is markdown shaped for that scale on purpose — and the rest of this page is how.
An early-stage project benefits from being clear about its boundaries. Here's where Thoth lives, and where it doesn't.
Human-readable and -writable, first.
The syntax is subtle enough to ignore — if you don't recognize something, the prose still reads without it.
A scalable way to think about content.
Works for one file. Works for a folder of ten thousand.
Honest about its second audience.
Language models read and write more markdown than people do. Thoth is designed for it.
Forgiving by default.
Thoth aims to render what you meant, not just what you typed. Strictness is available when you want it, not the default.
Not MDX.
Code doesn't belong in prose.
Not markup.
Content first, format last. If you can read it, it's working.
Not the “best possible” way to do anything.
A good enough way to do most things — and good enough is often exactly right.
Not Word.
Light on formatting, on purpose. Just enough to organize and emphasize, not every tool in the toolbox.
Three quiet additions, in service of one principle.
## Install {#install} Run the installer and confirm with `thoth --version`. ## Configure {#configure} Drop a `thoth.json` in your project root.
# Quick Start {./shared/setup.md#install} {./shared/setup.md#configure}
Click the <i class="ph ph-floppy-disk"></i>
Save button to commit your changes.Click the <:floppy-disk> Save button to
commit your changes.| Product | Price | In Stock | |--|--|--| | Pro | $199 | yes | | Plus | $99 | yes | | Starter | $29 | no |
{{./products.json | as:table}}
Each addition is small, ignorable when you don't know it, and consistent with the rest of the format.
Pull from CSV, JSON, or YAML. Filter, project, and format inline — without ever maintaining a hand-typed table.
{{./users.json | .users[role == "admin"] | as:table}}
Alignment, sizing, and flow handled with the same annotation pattern as the rest of the format.
{.float-right width=320} The system is composed of three layers: edge, application, and storage...
Highlight, strikethrough, superscript, subscript — all in plain text, all readable cold.
The endpoint returns ==success== or an ~~error~~ status. Water is H~2~O. Energy scales as E=mc^2^.
Configure how line breaks and whitespace are handled per file or per project. Preserve poetry. Collapse code samples.
--- linebreaks: preserve whitespace: collapse --- Each line in this section keeps its break, without trailing-double-space gymnastics.
A few things we know we want.
CommonMark is the baseline. What works in your current editor should mostly just work in Thoth.
The renderer aims for the closest reasonable output for what you wrote, not the strictest interpretation. When you want to dial that up, it's a choice you can make.
The things that don't have to be in the core won't be — diagram types, alternate renderers, output formats are all the kind of thing that lives outside the center.
The work, the discussion, and what we ship are all public from day one.
Different tools, same ground truth.
One source for the docs, the diagrams, the release notes, the internal wiki. Reuse a section by reference instead of copy-paste. Pull data from where it lives. Catch broken references before publish.
Markdown that's easy to drop into a build. CommonMark-compatible, plugin-friendly, with diagrams and structured data that live next to your code.
Documents with structure agents can address. Stable IDs, semantic tags, composable references. Round-trips cleanly through generation pipelines. Markdown that doesn't pretend its authors are all human.
A shared, file-based way to write content that travels across teams and tools. Open source from day one — never a vendor problem.
Markdown's strength has always been its flexibility, and we want Thoth to honor that as it grows. If the approach resonates, follow along and share feedback.
Stay up to date on our progress and key decisions. No spam, and we won't share your email. Powered by Buttondown.
Join the discussion on GitHub →