Skip to content

yasp-toolkit status

Show API health and authentication status for every registered yasp service, and the installed packages that provide commands.

Usage:

$ yasp-toolkit status [OPTIONS]

Options: * --help: Show this message and exit. Example output:

┏━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━┳━━━━━━━━━┳━━━━━━━━━━━━━┓
┃ API       ┃ URL                               ┃ Status ┃ Version ┃ Auth Status ┃
┡━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━╇━━━━━━━━━╇━━━━━━━━━━━━━┩
│ KernelGen │ https://compile.yasp.ai/kernelgen │ ready  │ 0.1.2   │ OK          │
│ Eval      │ https://compile.yasp.ai/eval      │ ready  │ 0.1.3   │ OK          │
│ Embedded  │ https://compile.yasp.ai/embedded  │ ready  │ 0.2.2   │ OK          │
└───────────┴───────────────────────────────────┴────────┴─────────┴─────────────┘

Column meanings:

  • Status — API health: ready, unreachable, or HTTP <code>.
  • Auth Status — token-verification result: OK, ERROR: <code> <reason>, ERROR: unreachable, or ERROR: <message>.

A service is fully available when both columns read ready and OK.

When something is wrong, status prints one line per problem under the table with the fix, for example:

→ No API key for https://compile.yasp.ai/api. Run `yasp-toolkit login` to create and store one (or create one at https://compile.yasp.ai/dashboard/tokens and store it with `yasp-toolkit keyring set https://compile.yasp.ai/api`, or export YASP_API_KEY).

It reports an unreachable API or token exchange (check YASP_API_HOST / --api-base-url), a missing API key, and a key that every API rejects, which usually means it has expired. A single service answering 401/403 usually just means your team has no access to it, so it gets no hint.

Under the hints, a second table lists every installed package that provides commands, with its version and the commands it mounted:

Command packages
┏━━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
┃ Package               ┃ Version ┃ Commands                                                                ┃
┡━━━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┩
│ yasp-agent            │ 0.7.0   │ login, status, keyring, embedded, dataset, eval, kernelgen, who-am-i, … │
│ yasp-activity-toolkit │ 0.7.0   │ activity                                                                │
└───────────────────────┴─────────┴─────────────────────────────────────────────────────────────────────────┘

A command another package replaces is listed under that package only. A command that could not be added is listed under the table with the reason, for example:

→ yasp-inspector-toolkit: `embedded explain` not mounted: no installed package provides `embedded`

This is expected when a package adds a command to a group whose own package is not installed. A package with no command added shows none mounted.