Higress AI Gateway Management

Overview

This skill allows you to manage the Higress AI Gateway via its Console API. The Console API runs at http://127.0.0.1:8001 and uses Session Cookie authentication (NOT Basic Auth).

Environment Variables

These environment variables are pre-configured in the Manager container. Access them directly in bash:

CODEBLOCK0

No need to set defaults - these are always available in the container environment.

Authentication

A session cookie file is stored at the path in ${HIGRESS_COOKIE_FILE} environment variable. Use it with curl -b "${HIGRESS_COOKIE_FILE}".

If the cookie expires, re-login:

CODEBLOCK1

Consumer Management

List Consumers

CODEBLOCK2

Create Consumer

CODEBLOCK3

Update Consumer (e.g., replace credential key)

CODEBLOCK4

Delete Consumer

CODEBLOCK5

AI Route Management

AI routes are internal routes managed via a separate API at /v1/ai/routes. They define LLM provider routing with model-level predicates, domain matching, and consumer auth. Do NOT use /v1/routes for AI routes.

List AI Routes

CODEBLOCK6

Get AI Route by Name

CODEBLOCK7

Create AI Route

The system initializes with a default-ai-route that has no modelPredicates — all model requests go through it. When the human asks to add a new provider, create a separate AI route with modelPredicates to distinguish which models go where:

CODEBLOCK8

When adding a new provider route with modelPredicates, also update the default-ai-route to add matching modelPredicates for its own models, so routes are unambiguous.

Key fields:

• - domains: which domain(s) this AI route serves (e.g. ${HICLAW_AI_GATEWAY_DOMAIN})
• upstreams: LLM provider(s) with weight and optional model mapping
• modelPredicates: match models by prefix/exact/regex (e.g. {"matchType":"PRE","matchValue":"deepseek"} routes all deepseek* models). Omit when only one route exists
• authConfig: consumer-level access control

Update AI Route (e.g., grant Worker access)

CODEBLOCK9

Delete AI Route

CODEBLOCK10

LLM Provider Configuration

List AI Providers

CODEBLOCK11

Create Provider

CODEBLOCK12

Update Provider (e.g., rotate API keys)

CODEBLOCK13

MCP Server Management

For creating, updating, listing, and deleting MCP Servers, as well as managing consumer access to MCP tools, see the mcp-server-management skill.

Important Notes

• - Auth Plugin Activation: First configuration takes ~40s, subsequent changes ~10s
• Version field: AI Routes and Providers have a version field. Always GET before PUT to get the latest version.
• Consumer version: Consumers do NOT have a version field
• MCP Server: See mcp-server-management skill for full details on creating and managing MCP servers