Skip to content

Add OrcaRouter as a built-in scan target - #324

Open
Marc-oss-hub wants to merge 1 commit into
msoedov:mainfrom
Marc-oss-hub:add-orcarouter-spec
Open

Add OrcaRouter as a built-in scan target#324
Marc-oss-hub wants to merge 1 commit into
msoedov:mainfrom
Marc-oss-hub:add-orcarouter-spec

Conversation

@Marc-oss-hub

Copy link
Copy Markdown

Add OrcaRouter as a built-in scan target

Adds OrcaRouter to the LLM endpoint dropdown, mirroring the existing OpenRouter entry.

What's included:

  • agentic_security/routes/_specs.py — new OrcaRouter API spec template (POST https://api.orcarouter.ai/v1/chat/completions, OpenAI-compatible, $ORCAROUTER_API_KEY) in both spec lists, plus a matching OrcaRouter entry in LLM_CONFIGS.
  • agentic_security/static/base.js — the same OrcaRouter spec template and LLM_CONFIGS entry for the frontend dropdown, kept index-aligned with the spec list.

Both the Python (_SPECS + LLM_CONFIGS/v1/llm-specs) and frontend (LLM_SPECS + LLM_CONFIGS) lists stay aligned at 15 entries each, with OrcaRouter appearing alongside OpenRouter.ai. OrcaRouter exposes an OpenAI-compatible /v1 chat/completions API, so the spec template uses the same messages format as the existing OpenAI/DeepSeek/Together entries and works with the scanner out of the box.

I'm an engineer on the OrcaRouter team. OrcaRouter is a secure, privacy-focused LLM gateway that unifies OpenAI-compatible model access behind a single API.

Mirrors the existing OpenRouter entry: adds an OrcaRouter API spec
template (OpenAI-compatible /v1 chat/completions) to the spec lists and
a corresponding entry in LLM_CONFIGS so it appears in the scan target
dropdown alongside OpenRouter.

Co-Authored-By: Claude <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant