The OpenRouter provider repository had an awkward starting point: its name said OpenRouter, but the implementation still contained Discord code. I corrected that and landed the first actual OpenRouter provider surface.1
The initial data sources listed models, looked up an individual model and read the balance endpoint. The openrouter_chat_completion resource added a request path with import support.
Make the first version usable
I included documentation and examples alongside the implementation, including model-comparison and documentation-generation examples. The provider needed enough surrounding material to show how the data sources and resource fitted together, not just Go types that happened to compile.
The PR records the build, vet and seven tests passing, with lint and test jobs in CI. That was the initial provider baseline, rather than a claim to cover every OpenRouter endpoint.
It also made the next gaps concrete. Once a completion could be created, there was room to inspect the resulting generation and its usage instead of treating the response text as the only useful output.