How it works
Run model calls through one accountable inference path.
Follow one call from your app through Inferock to the model that serves it, and see what Inferock records on the way back.
Three steps from call to accountable outcome.
- Your app
- Inferock
- Route selected for this callIntended alternate route for eligible requestsProvider and model
- Checks run against your requirementsResponse
Send model calls through one path
Keep your model choice while attaching request, route, schema, timing, usage, and response evidence to each event.
Attach receipts to what is observable.
Passive in path checks catch structural failures; active probes handle drift and baselines; some questions are flagged only when ground truth is available.
Review remedy status by mode.
The report shows what failed, what it cost, the evidence behind it, and whether it is report only or eligible for bounded Inferock Serve service credits under agreed terms.
- One API, major models
Use multiple providers and models through one endpoint without rebuilding every call path.
Measured public benchmark support today is OpenAI, Anthropic, Gemini Developer API, and pinned OpenRouter endpoints; additional providers are a design capability until their adapters and evidence gates ship.
The inference workflow, plus measured proof.
Dashboards show activity. Inferock shows which billed calls broke, what evidence supports the finding, and what happens next.
Illustrative record ยท sample values
Anatomy of a call record
- Request
- A response with a required answer field.
- Route
- Illustrative route: Inferock Watch with a connected provider account.
- Timing
- Not measured in this example.
- Usage
- Not measured in this example.
- Cost
- Not calculated in this example.
- Checks
- Required answer field missing.
- Remedy status
- Illustrative status: report only.Shows whether a failed call is report-only or eligible for Inferock Serve service credit under agreed terms.
- Monthly loss report
- See failed calls grouped by failure type, event count, estimated cost, evidence, and remedy status.
- Billing integrity signals
- Compare observable usage, cache, and charge fields so billing anomalies are visible instead of buried.
Routing alone is not accountability.
Inferock combines model access with the evidence needed to explain failed calls, costs, and Inferock Serve credit status.
| Category | What it usually answers |
|---|---|
| Routers | Which model should receive this request? |
| Observability tools | What happened in the trace, evaluation, or prompt workflow? |
| Cost tools | Where did spend go across teams, providers, and models? |
| Governance tools | Did the output meet policy, workflow, and review requirements? |
| Inferock | Which route served the call, what evidence was recorded, whether the call failed, and what remedy status applies? |