Resources

Manage datasets, abilities, deployments, and sessions

Resource commands follow the same verb-then-noun pattern:

eyepop get <resource>
eyepop create <resource>
eyepop patch <resource>
eyepop delete <resource>

Read

eyepop get accounts
eyepop get keys
eyepop get keys <prefix>
eyepop get datasets
eyepop get datasets <name-or-uuid>
eyepop get assets --dataset <dataset>
eyepop get abilities
eyepop get abilities <name-or-uuid>
eyepop get pops
eyepop get models
eyepop get deployments
eyepop get sessions
eyepop get instances
eyepop get evals <request_id>
eyepop get usage

get also answers to ls, list, and show, and you can drop it entirely for the common reads — eyepop datasets, eyepop abilities, eyepop models, eyepop pops.

get pops lists the Pops you saved in the dashboard alongside the built-in ones, and the OWNER column says which is which. A saved Pop is named by its alias, <your-namespace>.<name>:latest, shown in the POP column; a built-in is named by its short handle:

eyepop run --pop my-namespace.my-pop:latest --media-path image.jpg
eyepop run --pop people-common-objects --media-path image.jpg

--pop also takes the Pop itself, as a JSON or YAML file or inline, and an ability such as eyepop.person:latest, which runs as a one-component Pop:

eyepop run --pop ./pop.json --media-path image.jpg
eyepop run --pop '{"components":[{"type":"inference","id":1,"ability":"eyepop.person:latest"}]}' --media-path image.jpg

Search by name with -q, which get abilities, get datasets, and get pops all accept:

eyepop get abilities -q detector

Create

eyepop create dataset --name people
eyepop create asset --dataset people --media-path ./images --recursive
eyepop create ability --name people-counter --prompt "Count the people" --publish
eyepop create key --name ci
eyepop create deployment --model eyepop.person:latest

--publish publishes the new ability under your account's namespace and prints its alias, <your-namespace>.<task>.<name>:latest. That alias is how eyepop run --model, eyepop evaluate --ability, a Pop, and a deployment reference it; find it again in the ALIAS column of eyepop get abilities --mine.

create key prints the new key once and never again, so capture it there. A key lasts 30 days unless --expires-in names a lifetime in seconds. get keys lists yours by prefix, and under EYEPOP_API_KEY a bare get key checks the key you are using — whether it is still valid, when it expires, and what it may reach:

EYEPOP_API_KEY=eyp_... eyepop get key

Patch

Update a deployment in place and wait until it is healthy again:

eyepop patch deployment <session-uuid> --model eyepop.person:latest

Delete

Deletes are permanent. The CLI prompts for confirmation; --yes skips it.

Deployments and sessions take a display name, a session UUID, or a UUID prefix.

eyepop delete ability <name-or-uuid>
eyepop delete dataset <name-or-uuid>
eyepop delete key <prefix>
eyepop delete session <name-or-uuid>
eyepop delete deployment <name-or-uuid>

Removing an instance is not one of these, because it does not just remove a record from your account:

eyepop instance delete --yes

That tears down this machine's instance — the container, its volumes including the model cache, the pulled runtime image, the eyepop network, the instance root, the account's platform record, and — when the CLI installed one — the registry credential.

Next steps

• Command Reference — every resource command and its flags

• Run Inference & Evaluations — run the models and abilities you just listed