Smart Routing AI Model

curl https://ai.mihajlo.mk/api/smart-routing-ai-model/v1/responses \
  -H "Authorization: Bearer {serviceTokenHere}" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "smart-route-mini",
    "stream": true,
    "input": "Inspect the repository and suggest the next safe step."
  }'

The stream emits Responses API events such as response.created, response.output_text.delta, response.output_text.done, and response.completed. When a Codex-compatible client sends local tools, Smart Routing can also emit function_call items and then continue after the client sends back function_call_output.

This is the mode to use when you want Smart Routing to work as an agent for coding tasks. The API token only authenticates your Smart Routing service usage; local file access and command execution remain controlled by your Codex CLI configuration.

Higher plans are meant for more serious agent work: stronger public routing profiles, larger prompt budgets, and faster execution where the plan includes it.

Codex supports custom model providers in the user-level ~/.codex/config.toml. Add a provider that points to this API base URL and stores your token in an environment variable.

# ~/.codex/config.toml
model = "smart-route-mini"
model_provider = "ai_tools_router"

[model_providers.ai_tools_router]
name = "AI-tools Smart Routing"
base_url = "https://ai.mihajlo.mk/api/smart-routing-ai-model/v1"
env_key = "AI_TOOLS_ROUTER_API_KEY"
wire_api = "responses"

mkdir -p "$HOME/codex-ai-tools-test-home" "$HOME/codex-ai-tools-test-project"
export AI_TOOLS_ROUTER_API_KEY="{serviceTokenHere}"
cd "$HOME/codex-ai-tools-test-project"
CODEX_HOME="$HOME/codex-ai-tools-test-home" codex \
  -C "$PWD" \
  --dangerously-bypass-approvals-and-sandbox \
  -m smart-route-mini

Use wire_api = "responses" for Codex CLI. Smart Routing supports SSE streaming, function_call events, and function_call_output continuations on /v1/responses, which is what Codex-compatible agent clients need.

These options are passed to your local Codex CLI. Smart Routing only provides the model endpoint; command execution permissions are controlled by the CLI process on your machine.

If Linux sandboxing fails with bwrap or RTM_NEWADDR, the issue is local sandbox support. For a quick disposable test, use --dangerously-bypass-approvals-and-sandbox; for daily work, fix local sandbox/user namespace support or run in a properly isolated environment.

CODEX_HOME="$HOME/codex-ai-tools-test-home" codex \
  -C "$PWD" \
  -m smart-route-mini \
  -s read-only \
  -a on-request

CODEX_HOME="$HOME/codex-ai-tools-test-home" codex \
  -C "$PWD" \
  -m smart-route-mini \
  -s workspace-write \
  -a on-request

CODEX_HOME="$HOME/codex-ai-tools-test-home" codex exec \
  --skip-git-repo-check \
  -C "$PWD" \
  -m smart-route-mini \
  -s workspace-write \
  -a never \
  "Create hello.txt and then verify it exists."

CODEX_HOME="$HOME/codex-ai-tools-test-home" codex \
  -C "$PWD" \
  -m smart-route-mini \
  --dangerously-bypass-approvals-and-sandbox

Use a separate CODEX_HOME and a temporary project folder when testing a new provider setup. This keeps your main Codex configuration untouched.

mkdir -p ~/codex-ai-tools-test-home ~/codex-ai-tools-test-project
export AI_TOOLS_ROUTER_API_KEY="{serviceTokenHere}"
CODEX_HOME=~/codex-ai-tools-test-home codex exec \
  --skip-git-repo-check \
  --dangerously-bypass-approvals-and-sandbox \
  -C ~/codex-ai-tools-test-project \
  -m smart-route-mini \
  "Run pwd with the shell tool, then create hello.txt with a short hello message."