---
title: "nRouter.ai (@nrouterai) | Hashnode"
description: "Every model. One API key. Total control. Read the latest articles by nRouter.ai on Hashnode."
url: "https://hashnode.com/@nrouterai"
---

@nrouterai

# nRouter.ai

@nrouterai · Sunnyvale, USA · Joined August 2026

Every model. One API key. Total control.

[Website](https://nrouter.ai/)

### [Streaming Failure Recovery: Classify by What Escaped](https://nrouter.hashnode.dev/streaming-failure-recovery-classify-by-what-escaped?utm_source=hashnode&utm_medium=feed)

Streaming failure recovery: classify by what escaped The canonical broken streaming client is one catch block around the whole iterator: attempt, yield chunks, on exception start over. The loop tracks

3 min read · [nrouter.hashnode.dev](https://nrouter.hashnode.dev/streaming-failure-recovery-classify-by-what-escaped?utm_source=hashnode&utm_medium=feed)

[3d ago](https://hashnode.com/posts/streaming-failure-recovery-classify-by-what-escaped/6af6958e0556cd1f050c162e)

### [Thin Clients, One Policy: What nRouter's SDK Catalogue Gets Right](https://nrouter.hashnode.dev/thin-clients-one-policy-what-nrouter-s-sdk-catalogue-gets-right?utm_source=hashnode&utm_medium=feed)

Gateway SDKs usually fail in one of two directions. Either there is one first-class client (for the language the vendor's own team uses) and the rest of the ecosystem is told to speak raw HTTP, or eac

3 min read · [nrouter.hashnode.dev](https://nrouter.hashnode.dev/thin-clients-one-policy-what-nrouter-s-sdk-catalogue-gets-right?utm_source=hashnode&utm_medium=feed)

[3d ago](https://hashnode.com/posts/thin-clients-one-policy-what-nrouter-s-sdk-catalogue-gets-right/6af6945125696c31df0ea489)

### [Direct or nrouter/auto: The Model String Is the Whole Switch](https://nrouter.hashnode.dev/direct-or-nrouter-auto-the-model-string-is-the-whole-switch?utm_source=hashnode&utm_medium=feed)

Direct or nrouter/auto: the model string is the whole switch Most routing systems accumulate configuration surfaces: a header here, a dashboard weighting there, a client wrapper retrying its way acros

3 min read · [nrouter.hashnode.dev](https://nrouter.hashnode.dev/direct-or-nrouter-auto-the-model-string-is-the-whole-switch?utm_source=hashnode&utm_medium=feed)

[3d ago](https://hashnode.com/posts/direct-or-nrouter-auto-the-model-string-is-the-whole-switch/6af59042b2cd115c06966e01)

### [Deny Always Wins: Model RBAC in nRouter's Catalog](https://nrouter.hashnode.dev/deny-always-wins-model-rbac-in-nrouter-s-catalog?utm_source=hashnode&utm_medium=feed)

Most gateway access control is additive: grant a key a set of models, and hope nobody grants too much. nRouter's Models guide documents a stricter shape — allowlists and deny lists at three scopes, wi

3 min read · [nrouter.hashnode.dev](https://nrouter.hashnode.dev/deny-always-wins-model-rbac-in-nrouter-s-catalog?utm_source=hashnode&utm_medium=feed)

[3d ago](https://hashnode.com/posts/deny-always-wins-model-rbac-in-nrouter-s-catalog/6af58cfbc0f19f61f2b6e040)

### [LLM Routing with Jev 1.14: Keep the Judgment, Keep the Authority](https://nrouter.hashnode.dev/llm-routing-with-jev-1-14-keep-the-judgment-keep-the-authority?utm_source=hashnode&utm_medium=feed)

LLM routing with Jev 1.14: keep the judgment, keep the authority The useful way to read a judgment model is as a supplier of typed opinions, not as a junior operator. TypeSafe's Jev answers closed que

3 min read · [nrouter.hashnode.dev](https://nrouter.hashnode.dev/llm-routing-with-jev-1-14-keep-the-judgment-keep-the-authority?utm_source=hashnode&utm_medium=feed)

[4d ago](https://hashnode.com/posts/llm-routing-with-jev-1-14-keep-the-judgment-keep-the-authority/6af44b31bd1a4bf18539963e)
