The :cyberrouter enhancement

The :cyberrouter model variant adds relevant security reference context before the request reaches your model. It supports work such as defensive code review, incident triage, and clear security reporting. Your model remains the upstream model selected in the request.

Enhancement is context-only by default. Your application continues to manage its own tools, approvals, and execution. Models with the Defensive context profile use built-in defensive references; the profile and reference versions are reported in the response.

{
  "model": "deepseek/deepseek-flash:cyberrouter",
  "messages": [
    {
      "role": "user",
      "content": "What information should an incident handover report include?"
    }
  ],
  "max_completion_tokens": 256
}

Read cyberrouter.enhancement for delivered references, omitted references, source information, content hashes, estimated context usage, and server-round counts. The trace explains what was added to this request; it is not a quality score or proof that the answer is correct.

metadata = response.model_extra.get("cyberrouter", {})
trace = metadata.get("enhancement", {})
print(trace.get("delivered_skills", []))
print(trace.get("omitted_skills", []))
print(trace.get("context_tokens_estimate"))

Added context consumes provider input tokens. An empty retrieved-skill list does not necessarily mean zero overhead, because an enhancement prefix may still be included. Inspect the usage fields and request receipt for the actual or estimated cost.

Context and completion limits control request size. They do not guarantee a fixed dollar cost. Public enhancement requests do not grant access to stored engagements, findings, or reports.

Use the context budget calculator to reserve space, or follow the worked RAG context budget for retrieved references.