---
title: "Octri (@octri) | Hashnode"
description: "OpenAPI docs, SDKs in 10 languages, MCP tools, and opt-in SDK monitoring for API teams. Read the latest articles by Octri on Hashnode."
url: "https://hashnode.com/@octri"
---

@octri

# Octri

@octri · Joined October 2026

OpenAPI docs, SDKs in 10 languages, MCP tools, and opt-in SDK monitoring for API teams.

### [Why generated SDKs break silently, and how to make them observable](https://octri.hashnode.dev/why-generated-sdks-break-silently-and-how-to-make-them-observable?utm_source=hashnode&utm_medium=feed)

You generate an SDK from your OpenAPI spec, publish it to npm and PyPI, and integrators start building on it. Then it goes dark. Once that client library is running inside someone else's production ap

5 min read · [octri.hashnode.dev](https://octri.hashnode.dev/why-generated-sdks-break-silently-and-how-to-make-them-observable?utm_source=hashnode&utm_medium=feed)

[Oct 9](https://hashnode.com/posts/why-generated-sdks-break-silently-and-how-to-make-them-observable/6ac8f8995aadd7b1496772a3)

### [Publishing SDKs to npm, PyPI, Maven Central and the rest](https://octri.hashnode.dev/publishing-sdks-to-npm-pypi-maven-central-and-the-rest?utm_source=hashnode&utm_medium=feed)

Generating a client library is the easy half. Getting it into the place your users already look, under a name you can live with, is where the irreversible decisions are. Most of them are naming decisi

6 min read · [octri.hashnode.dev](https://octri.hashnode.dev/publishing-sdks-to-npm-pypi-maven-central-and-the-rest?utm_source=hashnode&utm_medium=feed)

[Oct 9](https://hashnode.com/posts/publishing-sdks-to-npm-pypi-maven-central-and-the-rest/6ac8f6e9ac15f54f1d86f0bb)

### [How to Generate API Documentation from an OpenAPI Spec (2026 Guide)](https://octri.hashnode.dev/how-to-generate-api-documentation-from-an-openapi-spec-2026-guide?utm_source=hashnode&utm_medium=feed)

Good API documentation decides whether a developer integrates your API in an afternoon or gives up before lunch. The reliable way to get there is to generate your documentation directly from your Open

7 min read · [octri.hashnode.dev](https://octri.hashnode.dev/how-to-generate-api-documentation-from-an-openapi-spec-2026-guide?utm_source=hashnode&utm_medium=feed)

[Oct 9](https://hashnode.com/posts/how-to-generate-api-documentation-from-an-openapi-spec-2026-guide/6ac8f6c0ac15f54f1d86effe)

### [Should you hand-write your SDKs or generate them?](https://octri.hashnode.dev/should-you-hand-write-your-sdks-or-generate-them?utm_source=hashnode&utm_medium=feed)

The case for hand-writing is better than generation advocates admit, and it has a shape. A hand-written client can be idiomatic in ways a generator cannot reach. It can name a method after what your u

5 min read · [octri.hashnode.dev](https://octri.hashnode.dev/should-you-hand-write-your-sdks-or-generate-them?utm_source=hashnode&utm_medium=feed)

[Oct 9](https://hashnode.com/posts/should-you-hand-write-your-sdks-or-generate-them/6ac8f6374b609c82bfc3631d)

### [MCP vs OpenAPI: they answer different questions](https://octri.hashnode.dev/mcp-vs-openapi-they-answer-different-questions?utm_source=hashnode&utm_medium=feed)

The question gets asked as though one is replacing the other, and the framing is wrong in a way that leads teams to build the wrong thing. OpenAPI is a description. It is a document that says what you

6 min read · [octri.hashnode.dev](https://octri.hashnode.dev/mcp-vs-openapi-they-answer-different-questions?utm_source=hashnode&utm_medium=feed)

[Oct 9](https://hashnode.com/posts/mcp-vs-openapi-they-answer-different-questions/6ac8f564a8748a7c2ddf2b6e)