openrouter.ai · openai ·
openrouter/free on openrouter.ai
not recommended4 of 7 cases passed
48/100trust score
Observed facts across five dimensions
- Protocol compatibilityAPI format: OpenAI-compatible · tool calls: normal · parameter check: passed (a request with tools came back normally)
- Agent usability4/7 cases completed
- Usage reportingThe relay reported token usage
- Performancetotal duration 22.7 s
- Difference from official baselineduration -40%; input tokens -46%; output tokens +94%
7 cases
| Case | Result | Latency | Baseline | Difference |
|---|---|---|---|---|
| Basic Tool I/O | Failed | 13.1 s | 8.6 s | +53% |
| Multi-File Synthesis | Passed | 9.7 s | 11.9 s | -19% |
| Model Context Synthesis | Passed | 2.8 s | 1.7 s | +67% |
| Single Tool Call | Passed | 5.6 s | 3.8 s | +46% |
| Chained Tool Calls | Passed | 4.6 s | 4.8 s | -3% |
| Error Retry & Recovery | Failed | 0.1 s | 3.9 s | -98% |
| Long-Context Recall | Failed | 1.1 s | 1.5 s | -27% |
Tokens
| Metric | Relay | Baseline | Difference |
|---|---|---|---|
| Input tokens | 29,068 | 53,632 | -46% |
| Output tokens | 1,502 | 774 | +94% |
Previous tests
The 0 tests before the latest.
| Date | Score | Passed |
|---|
How is this relay doing now? Test it with your key
Last tested 2026-10-29 (1 run). Relays change; a test shows how this one does right now (usually 1–3 minutes; the key is never stored).
Test it →The address is prefilled with the usual /v1. Change it if your relay uses another path.