What works without a licence

You can try Mockarty’s local CLI commands before connecting to a server. When you
connect with a token, the server supplies the limits for that installation.
A licence can open additional modules, but your administrator must also give
you access to them. This page helps you choose a path and understand a limit
message; Plans and feature access explains the modules.

Local evaluation (Anonymous)

Without a configured server and token, these CLI operations can run locally:
mock serving, API tests, load tests, fuzzing, and contract validation. They are
useful for a quick experiment or a small CI smoke test. Server features such as
shared history, team workspaces, test case management, and Kubernetes chaos
experiments require a connected installation.

The CLI enforces these local caps:

Use a server installation when you need shared state or a larger run. Data kept only by a
local process does not automatically move to that installation.

Connected free installation (Community)

With a server URL and token, the CLI asks the server for its limits. Without
an active commercial licence, the current server provides the same bounded
local feature set with larger caps: 10 stubs, 1,000 virtual users, 5 minutes,
25,000 iterations per virtual user, 10 fuzz executions, 50 native test steps,
and 100 Postman iterations. The server still checks access when a command
creates or changes shared resources.

The server response is authoritative. A connection failure or an older server
can make the CLI fall back to local caps. If a command reports a limit, check
which server and token that command used before repeating the run.

Licensed mode

A licensed server reports the modules included in its licence. The CLI uses
that response for local command limits; the server checks your personal module
grants and workspace role for shared operations. A licence does not give every
user permission to change every resource. Ask an administrator to check your
module grant if a command returns an access error.

The current module names and the difference between a module grant and a
workspace role are in Plans and feature access.

Connect the CLI

If an administrator has given you an API token, save a named connection:

mockarty-cli login --server https://mockarty.example.com --token "$MOCKARTY_API_TOKEN" --name team
mockarty-cli config get-contexts

Store the token in your CI secret store or shell environment rather than in a
script. For interactive OAuth login, see Sign in from the CLI.
Run mockarty-cli health to check server health; it does not report your
licence mode. The mockarty-cli tui auth screen shows its own authentication
state, while individual commands use the limits returned by the server.

When a command is blocked

1. Check the server URL and active context with mockarty-cli config view.
2. Check that the token belongs to the intended installation and workspace.
3. Read the command’s limit or permission message. A size cap and a missing
   module grant are different problems.
4. Ask an administrator to review Admin → Users and the licence only if
   the server connection is correct.

See CLI command reference for command options
and Administration for licence setup.