Skip to main content
An organization owns every other resource — agents, sessions, credits, keys. vetta login writes the active org onto your profile from GET /v1/me; --org org_… overrides it for one command.

Commands

Members are addressed by usr_ id, not by email — set-role and remove take the id from vetta org members. Only invite takes an email, because the user may not exist yet.

list

list and create are the two commands that need no org id — everything else reads it from the profile. Without one they fail fast:

create

The reply carries a working admin API key for the new organization, and its secret appears once. Store it before the terminal scrolls; there is no way to read it back.

use / show / update

show returns the org record including its live credit balance:

members

invite, set-role, remove

--role is validated client-side against the shared role enum, so a typo fails before anything is sent rather than coming back as a 400.