Octri vs ReadMe
Octri’s docs site puts AI chat, private docs, PDF export and a changelog that writes itself on every plan. The same subscription adds SDKs in up to 10 languages, monitoring and a status page, and still costs less than ReadMe Pro.
Written by Octri · Checked 16 October 2026
Summary
- Octri ahead
- 24
- Level
- 12
- ReadMe ahead
- 8
$49
a month for Octri’s first paid plan, with docs, SDKs and monitoring. ReadMe Pro is $250 a month billed yearly, and AI chat is $150 more.
4 in 1
docs, SDKs, an MCP server and monitoring on one subscription, at no extra cost.
Both build a docs site with an interactive reference from your spec. Octri writes that reference for you, keeps the changelog itself, and puts AI chat, private docs, PDF export, a landing page, roles and an activity log on every plan, where ReadMe asks for Pro, Enterprise or a $150 add-on.
Then the subscription keeps going: SDKs in up to 10 languages published under your name, error reporting inside every SDK, API logs kept for days and traced from client to server, and uptime checks with a status page. ReadMe leads on its collaboration and community tools (branches, live co-editing, two-way Git sync, recipes, forums), on readers seeing their own keys and logs, and on localization, and the table shows each one.
Docs, head to head
Octri against ReadMe, 44 rows from each product’s pricing page and docs on 16 October 2026. Octri is ahead on 24, level on 12, and ReadMe is ahead on 8.
| Feature | Octri | ReadMe |
|---|---|---|
| Writing and editing | ||
| Visual editor | Every plan, on the published page | Every plan |
| Guides in Markdown and MDX | Every plan, with built-in components | Every plan, with custom MDX components on Pro |
| Endpoint reference | Written for you: every endpoint, every field, errors by status | Built from your spec, with an AI agent that writes on request |
| Spec and docs quality checks | A quality score on every plan, weak endpoints named | AI linter on Pro, docs audit in preview on Pro |
| Fix the spec from the docs | Every plan, committed to your repository when GitHub is connected | Not listed |
| API changelog | Written from every spec change, on every plan | Hand-written posts, on Pro |
| Docs pages kept in Git | Spec sync on every plan, with spec edits committed back | Two-way sync of every page, on every plan |
| Branches, reviews and live co-editing | Draft and publish, with release history | Pro |
| Versioned docs | Growth | Pro |
| API reference | ||
| Interactive playground | Every plan | Every plan |
| HTTP request examples | Every plan, in several languages | Every plan, in several languages |
| Calls through your own SDK | Every endpoint, in each SDK language you publish | Not listed |
| Error guide per status code | Every endpoint, with cause and fix | Not listed |
| Readers’ own API keys filled in | Not available | Every plan, through JWT sign-in |
| Step-by-step recipes | Not available | Pro |
| SDKs | ||
| SDK generation | TypeScript, Python, Go, Java, Kotlin, Ruby, PHP, Rust, Swift and Dart, generated by you and published for your users | A TypeScript and JavaScript client each user generates locally |
| Registry publishing | Every plan: npm, PyPI, Maven Central, RubyGems, crates.io, pub.dev, plus Go, PHP and Swift tags | Not offered |
| Shaping the SDK | SDK Studio, per endpoint, with a live code preview | Not offered |
| Error reporting inside the SDK | Built in, tagged to the release | Not offered |
| Look and feel | ||
| Theme and layout | A choice of page layouts, your accent colour, light and dark code themes, text size | Themes on every plan |
| Landing page | Any page as the home page, on every plan | Pro, with templates on Enterprise |
| Custom components and CSS | Growth | Pro |
| Custom JavaScript | Growth, as head and body code | Enterprise |
| Remove the vendor’s branding | Business | Enterprise |
| Localization | One language per site | Localize on every plan, AI translations on Enterprise |
| AI and agents | ||
| AI chat for readers | Every plan, Free included | Ask AI, a $150 a month add-on |
| llms.txt | Every plan | Every plan |
| MCP server | 7 docs tools and a callable tool per endpoint, on every plan | Endpoint tools on every plan, docs search as an add-on |
| Tool export | MCP, OpenAI and Anthropic formats | Not listed |
| Publishing and access | ||
| Custom domain | Every plan | Every plan |
| Password-protected docs | Every plan | Pro |
| Reader sign-in | Enterprise, SAML | JWT on every plan, SAML and OAuth on Enterprise |
| PDF export | Every plan, any page | Pro |
| Redirect rules | Every plan: send a retired page to another, and keep old links working on rename | Pro |
| Status page and outages | Your own status page, and a docs banner when uptime checks fail | An Atlassian Statuspage integration on Pro |
| Discussion forums | Not available | Pro |
| Analytics and team | ||
| Docs analytics | Every plan | Every plan |
| API request logs | Every plan, kept 7 days on Free and up to 180 on Business | Every plan, kept 24 hours; longer history is $100 a month |
| Readers see their own request logs | Not available | Every plan, in the Developer Dashboard |
| Traces and latency targets | Every plan | Not listed |
| Roles and permissions | Every plan | Enterprise |
| Activity log | Every plan | Audit logs on Enterprise |
| Webhooks and a public API | Every plan, plus the octri CLI | API access on every plan, plus the rdme CLI |
| Dashboard single sign-on | Enterprise | Enterprise |
Only on Octri
9 features you will not find in ReadMe’s pricing page or docs.
SDKs you publish
TypeScript, Python, Go, Java, Kotlin, Ruby, PHP, Rust, Swift and Dart, released to their registries under your name.
SDKs shaped in a studio
Client shape, method names and file layout per endpoint, with the generated code redrawn beside each change.
Error reporting inside every SDK
A failure in your users’ apps reaches you with the SDK version, language and method, tagged to the release.
Uptime checks and your own status page
Checks generated from your spec, incidents on a status page on your domain, and a banner across your docs.
Traces from client to server
Follow one failing call from a user’s app into your handler, with latency targets per route.
An error guide for every status code
Each endpoint lists the errors it can return, with what causes each one and how to fix it.
A changelog that writes itself
Every spec change becomes a dated entry of endpoints added, removed and changed, with breaking changes flagged.
Docs edits that fix the spec
Correct an endpoint on the page and, with GitHub connected, the change is committed to your spec.
Tools for any agent framework
The MCP tool list exports in MCP, OpenAI and Anthropic formats.
SDKs you publish, in ten languages
ReadMe lets each of your users generate a JavaScript or TypeScript client on their own machine. Octri generates the SDKs once, in up to ten languages, and publishes them under your name.
ReadMe’s api package reads your spec and writes a typed client into the user’s project when they run it. It covers JavaScript and TypeScript, and nothing is published for you. Octri generates TypeScript, Python, Go, Java, Kotlin, Ruby, PHP, Rust, Swift and Dart from the same spec as your docs, and releases them to npm, PyPI, Maven Central, RubyGems, crates.io and pub.dev, with git tags for Go, PHP and Swift.
Every client comes with typed models and errors, auth from your security schemes, retries with backoff, pagination, idempotency and streaming. SDK Studio shapes them, with the generated code redrawn beside each change, and every endpoint page in your docs shows the call through your own SDK. The Free plan includes one language of your choice, Starter 2, Growth 4 and Business all ten.
- A GitHub repository per language, with every regeneration arriving as a pull request
- An optional test suite, and an optional CLI with a subcommand per endpoint
- Custom SDK code from Growth, kept through each regeneration by a normal merge
A reference that is already written
Both build an API reference with a playground from your spec. On Octri the reference arrives written, and the changelog keeps itself on every plan.
ReadMe renders your spec and offers an AI agent that writes when you ask it to. Octri writes the reference for you on import: every endpoint gets a description, every request and response field is explained, and each error is documented by status code with its cause and fix. Edits are stored per page, so when the spec changes only the endpoints that moved are rewritten.
On ReadMe a changelog is a set of posts you write, and it sits on Pro. On Octri every spec change becomes a dated changelog entry on every plan, listing endpoints added, removed and changed, with breaking changes flagged. A quality score names the weakest endpoints, and a fix made inside the docs is committed back to your repository.
Past 24 hours of logs
ReadMe’s Developer Dashboard shows API request logs once its Metrics SDK is in your backend, and keeps them for 24 hours. Octri’s monitoring keeps them longer and goes further.
ReadMe keeps request history and detailed logs for 24 hours on every plan, and sells longer history at $100 a month. Its strength is that a signed-in reader can see their own requests inside your docs.
Octri’s backend packages, in ten languages, keep raw events for 7 days on Free, 30 on Starter and up to 180 on Business, with structured logs, traces that follow a call from the client into your handler, latency and error targets per route, and N+1 query detection. On top of that, your SDKs report their own failures from your users’ apps, and uptime checks generated from your spec publish incidents to a status page on your own domain.
- Alerts for new issues, regressions and thresholds, to Slack or any webhook
- No third-party observability vendor in the path; data stored in the United Kingdom
- Monitoring ingest is never cut off at the allowance, so a bad day’s errors still arrive
AI chat and MCP, included
ReadMe sells its Ask AI chat as a $150 a month add-on, and its MCP docs search as an add-on too. Octri includes both on every plan.
Octri’s chat answers your readers from your published pages and your spec, on every plan, Free included. Its MCP server has seven tools for reading the docs (search, one endpoint in full, the endpoint list, guides, the changelog, your SDKs and the call in your own SDK) and one callable tool per endpoint, also on every plan.
ReadMe’s MCP server includes endpoint tools on every plan, and lists its docs search tools as an add-on. Octri’s server runs locally over stdio with credentials kept on the developer’s machine, or as a shared SSE server for a team, and its tool list exports in MCP, OpenAI and Anthropic formats.
Pro and Enterprise features, on every plan
Password-protected docs, PDF export, a landing page, roles and an activity log are on every Octri plan. ReadMe puts them on Pro or Enterprise.
Octri password-protects a docs site on every plan, and exports any page to PDF. Roles with granular permissions and an activity log come with every plan too, where ReadMe lists editor and viewer roles and audit logs on Enterprise.
Custom components and CSS arrive on Growth at $79 a month, custom head and body code on Growth as well, and white-label docs on Business at $249, which is still less than ReadMe Pro.
Also in the plan, at no extra cost
ReadMe’s subscription ends at the docs and their request logs. Octri’s keeps going: everything below is on the same plan, Free included, at no extra cost.
SDKs in up to 10 languages
Pick from TypeScript, Python, Go, Java, Kotlin, Ruby, PHP, Rust, Swift and Dart. Your plan sets how many, from one on Free to all ten on Business.
Error reporting inside every SDK
Failures in your users’ apps arrive with the SDK version, language and method, tagged to the release.
Uptime checks and a status page
Checks generated from your spec, and incidents on a status page on your domain and a banner in your docs.
A CLI and tests for your API
Optional, generated with the SDK: a command-line tool with a subcommand per endpoint, and a test suite.
More product, for less
ReadMe Pro is $250 a month billed yearly, before Ask AI. Octri Business is less, with all ten SDK languages and monitoring. Prices as published on 16 October 2026.
ReadMe Pro
$250
a month, billed yearly
- Docs with changelog, landing page, PDF export and private docs
- Custom MDX components and CSS, branches and reviews
- Ask AI chat, $150 a month more
- No SDKs to publish
Octri Starter
$49
a month, or $41.65 billed yearly
- Docs with chat, changelog, PDF export and private docs
- SDKs in 2 languages of your choice
- MCP server with docs and endpoint tools
- SDK errors, uptime checks, status page
Octri Business
$249
a month, or $211.65 billed yearly
- Everything in Starter
- SDKs in all ten languages
- Custom components, CSS and white-label docs
- 600 endpoints, SDKs on a CDN
Plan by plan
Octri’s yearly billing takes 15% off the base price. ReadMe bills Pro and Enterprise yearly.
| Plan | Octri | ReadMe |
|---|---|---|
| Free | $0. Docs site, one SDK language, 50 endpoints, monitoring, MCP, AI chat with 100 credits | Starter, $0. Custom domain, API reference, two-way Git sync, metrics, MCP, one version, one admin |
| First paid | Starter, $49 a month. Two SDK languages, 100 endpoints, 1,000 credits a month | Pro, $250 a month billed yearly. Five admins, then $20 each; changelog, private docs, PDF export, custom MDX and CSS |
| Middle | Growth, $79 a month. Four languages, 300 endpoints, versioning, custom code, components and CSS | No plan between Pro and Enterprise |
| Upper | Business, $249 a month. All ten languages, 600 endpoints, white-label, SDKs on a CDN | No plan between Pro and Enterprise |
| Top | Enterprise, custom. SAML single sign-on, unlimited endpoints | Enterprise, custom, billed yearly. Roles, SAML, audit logs, branding removal |
| Add-ons | An extra SDK language is $50 a month on Starter and Growth | Ask AI $150 a month; longer API log history $100 a month |
What three common setups cost a month
ReadMe’s column covers ReadMe only. Where a setup needs SDKs or monitoring, those come from other vendors at their own prices.
| Setup | Octri | ReadMe |
|---|---|---|
| Docs with an AI chat and password protection | Free, $0, covers both. Starter, $49, adds 1,000 chat credits a month | Pro, $250, plus Ask AI at $150 |
| Docs plus TypeScript and Python SDKs | Starter, $49. Both languages are in the bundle | Pro, $250, plus an SDK generator from another vendor |
| Docs, SDKs in all ten languages, API logs past a day, uptime checks and a status page | Business, $249 | Pro, $250, plus $100 for log history, an SDK generator and a monitoring vendor |
Moving from ReadMe
The move starts from two things a ReadMe project already has: the OpenAPI file its reference is built from and, with bi-directional sync, its pages as Markdown in Git.
How the move works
Stage 1
Bring it in
You
Upload the OpenAPI file your ReadMe reference is built from, or connect the repository it lives in.
Octri
Writes a reference page for every endpoint, with the playground, search and chat switched on.
Stage 2
Fill it out
You
Paste your guides into the MDX editor from the Markdown that bi-directional sync keeps in Git, and pick your SDK languages.
Octri
Generates your SDKs from the same spec and shows the call through them on every endpoint page.
Stage 3
Go live
You
Connect GitHub, publish, and point your custom domain at Octri last.
Octri
Rebuilds the draft every time a spec change merges, ready for you to publish.
Which should you choose?
Choose ReadMe
Choose ReadMe if several writers edit your docs at once through branches and reviews, if your readers should see their own API keys and request logs inside the docs, or if recipes and a community forum are part of how you support developers.
Choose Octri
Choose Octri if you want docs that write themselves and stay right. Every endpoint arrives documented from your spec, with an error guide for each status code, a changelog that updates with every spec change, and fixes made on the page committed back to the spec. Readers get AI chat, password-protected access and PDF export on every plan, without a $250 Pro plan or a $150 add-on.
Then comes the rest of the subscription. The same spec also becomes SDKs in up to 10 languages published under your name, error reporting inside every SDK, API logs traced from client to server, uptime checks and a status page, all at no extra cost. On ReadMe, each of those is another vendor and another bill.
Questions
ReadMe’s Starter plan is free. Pro is $250 a month billed yearly, with five admins and $20 for each one after that, and Enterprise is priced by quote with yearly billing. Ask AI is $150 a month on any plan, and API log history past 24 hours is $100 a month. Octri’s paid plans start at $49 a month, or $41.65 billed yearly.
Other comparisons
Octri vs
Mintlify
A docs site plus first-party SDKs in ten languages from the same spec, and the monitoring those SDKs make possible.
Compare
Octri vs
Redocly
A docs site written from your spec, SDKs in ten languages, a hosted MCP server and monitoring, with AI chat on every plan.
Compare
Octri vs
Docusaurus
API docs written from your spec and hosted for you, plus SDKs in ten languages, a hosted MCP server and monitoring.
Compare
Octri vs
Scalar
Docs, SDKs and a hosted MCP server, with all ten SDK languages in the plan and monitoring that Scalar does not offer.
Compare
Octri vs
Fern
Docs and SDKs from one spec, any of ten languages on the free plan, and monitoring inside every client.
Compare
Octri vs
Stainless
Takes new projects, reads stainless.yml and adds monitoring inside every client it generates.
Compare
Octri vs
APIMatic
SDKs in ten languages included in the plan, a docs site written from your spec, a hosted MCP server and monitoring.
CompareSide by side
All of them
Every comparison, grouped by what each tool does.
Compare
Written by Octri, from each vendor's public pages and our own testing, checked 16 October 2026. Products change often, so confirm anything that matters to you on the vendor's own site. Product names are the trademarks of their owners, used here only to identify their products. Octri is not affiliated with or endorsed by any of them.
Spotted something out of date? Write to founders@octri.dev and we will correct it.
Try it on your own spec
Upload the OpenAPI file your ReadMe reference is built from on the Free plan, and compare the result with your current docs.