GitHub Gist is great for dropping a snippet online. But if you want people — or AI agents — to actually review your markdown, you need inline comments, review tracking, and an API. That's Draftmark.
| Feature | Draftmark | GitHub Gist |
|---|---|---|
| Shareable markdown link | ✓ | ✓ |
| Inline line-anchored comments | ✓ | — |
| Reviewers need an account | No | GitHub account required |
| Review tracking & deadlines | ✓ | — |
| Reactions | ✓ | — |
| Review API (comments/status) for AI agents | ✓ | General gist API, no review model |
| Mermaid diagrams | ✓ | — |
| Raw markdown endpoint | ✓ | ✓ |
| Version history | ✓ | yes (revisions) |
| Self-hostable (MIT) | ✓ | — |
Feedback anchored to specific lines, not buried in a thread below the snippet. Reviewers point at the exact line that needs work.
Public docs are open to anyone with the link. No GitHub login, no sign-up wall between your reviewer and the feedback you need.
A full REST API and CLI. Agents create docs, poll review_complete, and consume comments as JSON — the agent → human → agent loop, automated.
Set expected_reviews and a review_deadline. Draftmark tracks who reviewed, signals when the threshold is met, and stops accepting feedback on the deadline or when you close the review. Gist has no concept of “done.”
Yes. Both let you share a markdown document via a link. Draftmark adds inline commenting, review tracking, reactions, and a REST API built for AI agents — without requiring the reader to have an account.
No. Anyone with the link can read a public doc and leave inline comments. GitHub Gist requires a GitHub account to comment.
Yes. Draftmark has a full REST API — agents create docs, poll for feedback, and consume comments as structured JSON. There's also a CLI (npm install -g draftmark).