Lesson 2

How to use every CLI command

Every Intempt CLI command, its flags, and whether it needs credentials.

Video comingThe video is being filmed. The steps below are the whole lesson.

In this lesson

  1. 1Run intempt --help and read the full command list.
  2. 2With no credentials set, run intempt status, then intempt generate, then intempt validate, and note there is no auth prompt.
  3. 3Run a credentialed command without a key, for example intempt content generate-email "spring sale", and read the failure.
  4. 4Re-run it with --api-key, or export INTEMPT_API_KEY, or run intempt login once. Blur the key on camera.
Read the reference docs for this lesson

Setup checklist

The 18 steps to wire Intempt into your stack, from installing the CLI to an agent that can work in your project. Tick them off as you go; your ticks stay in this browser.

Open the setup checklist (PDF)

0 of 18 ticked

You are done when

  • intempt --version prints 0.1.2 or newer and intempt init writes intempt.yaml.
  • intempt status and intempt generate run with no credentials; a content command fails without a key and succeeds with one.
  • tools/list count is read off the screen, then changes after setting INTEMPT_MCP_TOOLS and restarting.
  • One profile shows newly filled outside fields.

Your tech stack and tools

The core stack (everything you actually need)

Highly recommended optional upgrades that level up your work

The CLI and MCP server are free and open source. Enrichment uses AI credits; an email check costs 1 credit.