Openviking Controlplane

OpenViking Control Plane (ov-cp)

ov-cp is the CLI for the OpenViking control plane (topapi). It manages OV collections (libraries) and shares its core with the mcp-server-openviking-controlplane MCP server, so behavior is identical.

Setup

Install once (from the package dir): uv sync (or pip install -e .).

Configure via env vars (CLI flags -k / -e / --project override them):

export AGENTPLAN_API_KEY=ark-xxxxxxxx
# VIKING_ENDPOINT defaults to the public gateway — leave it unset for normal use.

The default endpoint is the reserved public gateway (not open yet). Override VIKING_ENDPOINT (or -e) only for testing — e.g. point it at a kubectl port-forward of the data-plane service. The full request URL is {endpoint}/api/openviking/{Action}.

Commands

ov-cp list                       # list collections (optionally --project X)
ov-cp get     <ResourceID>       # collection info (Status, models, version, ...)
ov-cp usage   <ResourceID>       # file counts / hourly CNY and AgentPlan AFP estimate
ov-cp api-key <ResourceID>       # default user's plaintext data-plane key
ov-cp api-key <ResourceID> --user-id xiaohong  # selected user's plaintext key
ov-cp create  --name my_kb       # create a collection (see below)
ov-cp update  <ResourceID> --description "..."   # update fields / switch billing
ov-cp update  <ResourceID> --model-api-key ark-xxx  # overwrite AgentPlan model key
ov-cp delete  <ResourceID> --yes # delete (irreversible; uninstalls the Helm release)

# users of an enterprise-tier library (key must be associated with the library):
ov-cp user list     <ResourceID>                     # users (ApiKey is masked)
ov-cp user list     <ResourceID> --role user --page 1 --limit 20
ov-cp user register <ResourceID> xiaohong            # new users always get role=user
ov-cp user update   <ResourceID> xiaohong --regenerate-key
ov-cp user delete   <ResourceID> xiaohong --yes      # revoke a user's credential

After user update --regenerate-key, fetch the replacement with api-key <ResourceID> --user-id <UserID>; the update response only confirms success and does not contain the new key.

update --model-api-key <ark-key> overwrites the library's AgentPlan MODEL credential; VLM and Embedding always share one key, and the library's other credentials are replayed unchanged. Only pass a key the user gave you for this purpose — it REPLACES what is stored. A library with no AgentPlan model credential is refused rather than reshaped.

Without that flag update sends no model configuration at all. Against a control plane that still rebuilds both models on every update (it rejects a metadata-only request with apikey is empty), update reads the library's own credentials back and replays them once, reporting it in the response Note. A non-AgentPlan credential stored without an ApiKeyID cannot be replayed — the update is refused rather than guessed at.

In a terminal, output defaults to structured Rich views. Pipes and redirects automatically receive standard JSON, so ov-cp list | jq ... and command substitution remain safe. Use the global --json, --output json-compact, or --output pretty flags to force a mode. Errors print Error [Code]: Message to stderr with exit code 1. ov-cp --help and ov-cp <cmd> --help work without any config.

usage keeps EstimatedCosts for compatibility and adds EstimatedBilling. That object identifies the hourly period and CNY estimate; AgentPlan-paid collections also include the AFP amount and business scenario.

Creating a collection

⚠️ Billable + requires the account to have AgentPlan deduction activated (else ProductUnordered). Confirm with the user before creating. Max 20 libraries/account.

The public create command always uses the AgentPlan model path and the configured AgentPlan key. It does not expose model source, model parameters, model credentials, or an OpenViking image-version override.

ov-cp create --name my_kb
# enterprise tier (higher capacity, enterprise billing rates):
ov-cp create --name my_kb --version enterprise

--version is developer (default) or enterprise; any other value is rejected locally before the request.

Billing (--pay-type / --seat-id)

--version and billing are orthogonal: the tier sets the hourly RATE (developer 5 AFP baseline, enterprise 25 AFP baseline), --pay-type sets WHO PAYS. Both create and update take the same two flags (update is how you switch billing later, or re-bind after a seat was unbound).

ov-cp create --name my_kb                                    # default: personal AFP pays
ov-cp create --name my_kb --version enterprise \
  --pay-type agentplan_enterprise --seat-id seat-2026xxxx    # that seat's AFP pays
ov-cp create --name my_kb --pay-type volc_pay                # explicit website PAYG
ov-cp update <RID> --pay-type volc_pay                       # switch billing later

• Omitting --pay-type on create defaults to agentplan_personal (AFP deduction from the account's personal AgentPlan) — volc_pay (billed to the Volcano account) must be an explicit choice. ⚠️ Accounts with no personal plan (e.g. enterprise seat keys) must not rely on the default: the library binds a non-existent personal plan, deduction fails and the library is disabled. The CLI prints a note.
• The personal/enterprise choice is otherwise explicit — never guess it from the key.
• --seat-id is required with agentplan_enterprise and forbidden otherwise. The user must copy it manually from the Ark console seat-management page (no lookup API). The server does NOT verify the seat exists — a typo only surfaces at the next hourly deduction, which then disables the library.
• empty_pay (unbound) exists server-side but is not offered: such a library is unusable and auto-cleaned after 30 days.

Cold-start chain (create → use the library)

RID=$(ov-cp create --name my_kb | python3 -c 'import sys,json;print(json.load(sys.stdin)["ResourceID"])')
# Poll until provisioned; api-key times out while Status is INIT.
ov-cp get "$RID"        # wait for "Status": "READY"
ov-cp api-key "$RID"    # -> the plaintext data-plane key for the library

The returned ApiKey is the library's data-plane key. Use it as Authorization: Bearer <key> against the library's data-plane (e.g. GET {endpoint}/health, GET {endpoint}/api/v1/system/status, GET {endpoint}/api/v1/fs/ls?uri=viking://).

Notes

• Only Authorization: Bearer is accepted (no X-API-Key).
• list / get / usage are read-only. delete is destructive but, like those reads, is not gated by AgentPlan; create and api-key are gated.
• get/usage/api-key/delete/update and all user * take a ResourceID (e.g. ov-xxxxxxxx).
• user * manages the multiple users of an enterprise-tier library and needs the AgentPlan key to be associated with that library (else the backend rejects it). user list returns each user's masked ApiKey; for a plaintext data-plane key use api-key <ResourceID> --user-id <UserID>.
• Extra headers: pass -H 'Key: Value' (repeatable) or set VIKING_EXTRA_HEADERS to a comma-separated Key: Value list — e.g. -H 'x-tt-env: lujiakun' for swim-lane routing. Authorization / Content-Type are protected and ignored.