Connect to the coordinator

The console talks to the coordinator through /api/, same origin — no CORS and no key in the URL. The key lives in this tab only and disappears when you close it.

No key yet?

On the coordinator, with an admin identity:

vision.cluster apikey create --url https://COORDENADOR --identity admin --name "consola" --role client

Dashboard

machines on the network

id	vendor	models	ms/token	load	contract

coordinator metrics

—

Jobs

A job is a unit with a digest; verification is its re-run on another machine. verify_rate takes a number (0–1) or auto.

job status give the id you got back

—

Audit

The trail is hash-chained: every entry carries the hash of the one before it. Verifying it is not trust — it is re-computation.

—

Keys

Roles: client submits, auditor only reads audit and metrics, admin issues and revokes. Agents use certificates, never keys.

—

Plan

The planner ships as a library and decides format, split and placement from the measured inventory. It is not exposed over HTTP yet, and this page will not invent a number.

Today, from code

from vision.cluster.planner import choose, schedule

POST /v1/plan is the next step; this screen will use it.