Wanted
Three things on the OpenRouter backend:
- Response id. Each evaluation returns OpenRouter's
id (for example gen-dec-...), along with provider and the dated model it served, once they are validated. The TypeSafe backend returns neither id nor provider, so these fields are optional.
- Session and trace data. Callers can forward
session_id (a string of at most 256 characters) and metadata (the trace keys trace_id, trace_name, span_name, generation_name, parent_span_id) (request reference). The request schema rejects unknown keys today, so this needs explicit, validated options, sent only to OpenRouter.
- Context window. Document that Jev on OpenRouter has a 32,000-token context window, next to the byte-based
maxInputBytes limit.
Nothing from upstream reaches a caller without validation, and error messages never contain submitted state or response bodies.
Wanted
Three things on the OpenRouter backend:
id(for examplegen-dec-...), along withproviderand the datedmodelit served, once they are validated. The TypeSafe backend returns neitheridnorprovider, so these fields are optional.session_id(a string of at most 256 characters) andmetadata(the trace keystrace_id,trace_name,span_name,generation_name,parent_span_id) (request reference). The request schema rejects unknown keys today, so this needs explicit, validated options, sent only to OpenRouter.maxInputByteslimit.Nothing from upstream reaches a caller without validation, and error messages never contain submitted state or response bodies.