Neurometric is now a listed provider on TrustedRouter. If you already route inference through TrustedRouter, our models are available to you today — no new account, no new SDK, no new base URL.
What Is TrustedRouter?
TrustedRouter is an inference gateway in the same family as OpenRouter: one OpenAI-compatible API, one base URL, and hundreds of models and routes behind it. You point your existing client at the gateway and swap model strings instead of rewriting integrations every time you want to try a different provider.
What makes it interesting is the trust posture. TrustedRouter keeps no record of what you route — no prompt or output logs, by design, and the gateway is attested and fails closed rather than silently degrading. It publishes a live status page and a continuously sampled performance leaderboard, so latency and uptime claims are measured rather than asserted. There’s also a documented migration path from OpenRouter for teams that want to move without a rewrite.
For anyone who has spent time explaining to a security team why prompts containing customer data are being logged by a third party, that combination is worth something.
What We’re Serving Today
We’re live with three small models on prepaid routes:
ibm-granite/granite-4.1-8b— 32K context, $0.0525/1M prompt and $0.105/1M completionqwen/qwen3-vl-8b-instruct— 262K context, vision-capableqwen/qwen3-vl-8b-thinking— 32K context, reasoning traces
Early measured numbers on our routes: 863 ms p50 time-to-first-token on Granite and 100% uptime across the sampling window. Our listed policy note is accurate about what we do and don’t guarantee — upstream trace logging is disabled, prompts and completions are not written to observability or object storage, and we retain only aggregate request counts and token totals. That’s a no-store posture, not contractual ZDR, and we’d rather say so plainly than let people assume more than we’ve committed to.
Task-Specific Models Are Coming Next
Small general-purpose models are the entry point, not the thesis. The reason we build the way we do is that most production workloads aren’t “chat” — they’re a narrow, repetitive task where a tuned 8B model matches or beats a frontier model at a fraction of the cost.
Three task-specific models from our model marketplace we expect to list on TrustedRouter in the coming weeks:
Text-to-SQL — natural language to correct, schema-aware queries against a known database, tuned for join accuracy rather than conversational fluency.
Structured extraction — pulling typed JSON out of invoices, contracts, and claims documents against a supplied schema, with predictable failure behavior on missing fields.
Support intent classification — routing inbound tickets to the right queue and priority, the kind of high-volume, low-token task where per-call cost dominates everything else.
Each is graded against our proprietary task benchmark corpus, so you can see how a specialist performs on your task class before you route production traffic to it.
If you want to try the current models, grab a key at TrustedRouter and use neurometric as the provider. If you have a task class you’d like us to build for, tell us — that’s how the roadmap gets set.