Project commands
Confirm your identity and list or inspect the Microtica projects your credential can access, using the microtica whoami and project commands.
These commands tell you who you are and which projects your credential can reach. A project is the top-level container for your environments, pipelines, and apps, so you'll usually start here to grab a project id.
whoami
Show the identity behind your stored API key and check that the API is reachable. It reads the key locally and makes one call to confirm it still works.
microtica whoamivia: apikey
api key prefix: mic_d60bea1d
api reachable: true
projects visible: 12api key prefix identifies the stored key without exposing it, and projects visible is the number of projects your key can access.
project list
List every project your credential can access. This command works across your account, so it doesn't need a project id.
microtica project listid name owner
-------------------- -------- -----------------
z2wti53si2xk61nehxds Acme Web owner@example.comGrab an id here to pass as --project or to set MICROTICA_PROJECT_ID.
project get
Show the full record for one project, including its payment plan.
microtica project get <projectId>Add --json for the complete object, or --query to pull specific fields:
microtica project get z2wti53si2xk61nehxds --query "paymentPlan.name"Next steps
Command reference
Every Microtica CLI command, grouped by what it manages — projects, environments, applications, pipelines, components, Git, and logs.
Environment commands
Clone, deploy, wait on, and tear down Microtica environments and their resources from the CLI, with partial deploys and config management.