Skip to main content
Goal: Learn the fundamentals of OpenRouter by building a TypeScript chat app that sends messages and streams responses through OpenRouter. Outcome: A working multi-turn conversation loop that can talk to any of the 600+ models available on the platform by changing a single string.
Want to get started faster? Copy this prompt into your coding agent.

Prerequisites

1. Create a project and install the SDK

Set up a new Node.js project and add the OpenRouter client SDK. The SDK is ESM-only, so set the package type to module. Install tsx so you can run the TypeScript examples directly.

2. Send your first message

Create chat.ts with a client instance and a single chat completion request. The apiKey reads from the environment so you never hard-code credentials.
Run it with your API key:
You should see a single text response printed to the console. The SDK returns token usage in camelCase fields such as promptTokens and completionTokens. The completion.choices array follows the same shape as the Chat Completions response.

3. Stream the response

Streaming returns text as it is generated instead of waiting for the full response. Pass stream: true and iterate over the returned async iterable. Each chunk contains a delta with the new text fragment.
Text now prints incrementally. See the Streaming reference for the full SSE event format.

4. Add multi-turn conversation

Multi-turn works by sending the full message history with each request. The model uses all previous messages as context. Append each user input and assistant response to a messages array before the next call.
Run the file and type messages. The model remembers prior turns because the full messages array is sent with each request. Type exit to quit.

5. Swap models

OpenRouter gives you access to hundreds of models through one API. Change the model string to switch providers — no other code changes needed.
Browse all available models at openrouter.ai/models or query the Models API programmatically.

Check your work

  • npx tsx chat.ts prints a streamed response to the console
  • A multi-turn conversation maintains context across turns (ask a follow-up that references a previous answer)
  • Changing the model string switches to a different provider with no other code changes
  • The non-streaming response includes a usage object with promptTokens and completionTokens

Next steps

  • Connect a coding agent to OpenRouter
  • Explore the Agent SDK for built-in multi-turn loops and tool execution