We have launched a new program with OpenRouter that allows OpenRouter users to bring their own keys and run them through Backboard’s stateful API. This unlocks persistent memory, best-in-class RAG, and long-lived agent state without changing how teams already source models.

What’s new

• Bring Your Own Key (BYOK)
  Use your existing OpenRouter keys directly on Backboard. No new provider contracts, no model lock-in.

• Stateful API on top of OpenRouter
  Requests gain durable memory, session continuity, and long-running thread state across calls.

• Integrated RAG and memory
  Pair OpenRouter’s model access with Backboard’s production-grade retrieval, memory persistence, and tooling.

Make everything stateful

Most OpenRouter workflows are stateless by default. That is fine for single prompts but breaks down for agents, assistants, and real applications. By layering Backboard underneath, OpenRouter users get memory and state as first-class primitives, not bolted-on features.

This also avoids a common tradeoff. Teams no longer have to choose between flexible model routing and strong memory architecture. You get both.

Example use case

A small developer team builds a research agent using OpenRouter to test multiple models. With BYOK on Backboard:

• Conversations persist across sessions

• Retrieved documents stay grounded over time

• Agent behavior improves with accumulated memory instead of resetting every call

No changes to model selection. No custom memory system to maintain.

Who this is for

• Developers already standardized on OpenRouter

• Teams experimenting with many models but needing consistent state

• Builders who want memory-native agents without managing infrastructure

Getting started

1. Connect your OpenRouter key in Backboard

2. Enable stateful threads and memory

3. Start building agents that remember

Documentation covers supported models, RAG configuration, and stateful workflows.