Your progress is only saved in this browser. to protect it and pick up on any device.

Connect a Postman API key to check your work

You do each step in Postman, then LiftOff uses your key to look at your workspace and confirm it's done. Connect once and it works for every module. Your key is saved in this browser and is only used to check your work in Postman.

Mission Trajectory
0 / 12·0%Pre-launch
  1. 1Launch
  2. 2Orbit
  3. 3Transit
  4. 4Flyby
  5. 5Return
  6. 6Splashdown
1

Health Check & Registration

Confirm the Artemis API is up, then register as crew. Your agent sends both requests from the collection it generated, using your artemis.local environment.

  1. Send this prompt. Your name and email are prefilled from your profile; click them to edit:
text
Check that the Artemis API is up with the Health check request of the "Artemis Mission Control" collection, using the artemis.local environment. Then register me as crew with the Register a new crew member request, with name "" and email "". Show me the status code of each call and the full registration response, unmasked: this is a training key and I need to copy the exact api_key value from it.

Watch your mission progress on the launch graphic above, or open the step counter in the bottom-right corner for a closer look as you move through the steps.

  1. The registration response holds your callsign, your api_key and a sigil (an SVG badge). Paste the api_key into the field below (you can paste the whole line, quotes and spaces are cleaned up). LiftOff keeps it in this browser session only, reuses it for every later validation, and lets you copy it into the next step without selecting it again.

Troubleshooting: If {{baseUrl}} is not resolved or you get a connection error, tell your agent to send the requests with the artemis.local environment. The generated collection defines baseUrl as a reference to itself, so it only resolves when the environment is used.

2

Store the Crew API Key Safely

Your crew API key authenticates every later request. Keep it out of git and out of the cloud environment. You type it yourself into a masked prompt, and from here on your agent only references it, never copies it.

Pick one path. Your choice is remembered, and every later step shows only that path.

Your API key path
Pick one and later steps only show that path.

Option A — Vault (Solo, Team and Enterprise plans)

  1. Create the secret yourself in your terminal, from the repo root. The CLI shows a masked prompt: use Copy my Artemis API key below, paste it and press Enter. Nothing is echoed, and only the secret's name and ids are printed.
No Artemis API key saved in LiftOff yet. Enter the api_key from your registration response in step 2.1 and validate it, then come back here to copy it.
zsh — ~/artemis-mission-control-agent
postman secret create ARTEMIS_API_KEY --terminalpostman secret create ARTEMIS_API_KEY --terminal
0/1 run
  1. Ask your agent to link the secret to the environment variable. It never sees the value:
text
I just stored my crew API key as a shared-vault secret named ARTEMIS_API_KEY. Link it to the apiKey variable of the artemis.local environment by reference, without ever reading the value. Do not ask me for the key, do not print it and do not write it into any file. Then show me the apiKey entry in the environment file and sync my work to my Postman workspace.
  1. Check the YAML: apiKey should hold secret and vault ids, not your key.

  2. Check it works with this prompt. Expect 200 OK with your callsign and mission status:

text
Call GET /mission with my crew API key and show me the status code, my callsign and my mission status. Authenticate by sending the x-api-key header explicitly set to {{apiKey}} from the artemis.local environment (a vault-linked secret the Postman CLI resolves itself), overriding the empty x-api-key header saved in the requests. Never print the key or write it into a file.

Option B — Env var (Free plans)

  1. Put the key in a shell variable. The prompt is masked: use Copy my Artemis API key below, paste it and press Enter. The variable only exists in this terminal, so repeat this in any new terminal, and start your agent from a terminal where it is set.
No Artemis API key saved in LiftOff yet. Enter the api_key from your registration response in step 2.1 and validate it, then come back here to copy it.
zsh — ~/artemis-mission-control-agent
read -s ARTEMIS_API_KEY && export ARTEMIS_API_KEYread -s ARTEMIS_API_KEY && export ARTEMIS_API_KEY
0/1 run

On Windows PowerShell, use $env:ARTEMIS_API_KEY = "<your key>" instead.

  1. Leave apiKey empty in the environment file. There is nothing more to push.

  2. Check it works with the same prompt as above (start your agent from this terminal). Expect 200 OK with your callsign and mission status:

text
Call GET /mission with my crew API key and show me the status code, my callsign and my mission status. Authenticate by sending the x-api-key header explicitly set to the ARTEMIS_API_KEY environment variable, overriding the empty x-api-key header saved in the requests. Never print the key or write it into a file.

From here on, every prompt asks your agent to use the key by reference: the apiKey variable of artemis.local on the Vault path, or the ARTEMIS_API_KEY shell variable on the Env-var path. You never paste the key into a prompt.

Important: This is a training key. Never put it in a committed file or in the cloud environment value, and never paste it into an agent prompt.

Troubleshooting 401 errors:

  • Vault path: if the API answers Missing API key, the vault reference did not resolve. Ask your agent to check that the secret exists (it never sees values), or fall back to the Env-var path, which works on every plan.
  • Env-var path: run echo "${#ARTEMIS_API_KEY}" to confirm the variable is set in the terminal your agent was started from.
  • If creating the secret is refused or unavailable, your plan has no Shared Vault. Use Option B.

After you validate, your mission clearance loads on its own from the key you entered in the previous step. If that key was rejected, LiftOff clears it and asks you to paste it again.

3

Build Mission Dashboard

A terminal has no Visualize tab, so your agent builds your dashboard twice: a text dashboard that prints in the CLI every time the request runs, and a self-contained HTML page you open in a browser.

Key path
  1. Send this prompt to your agent:

Vault path

text
On the "Get mission overview" request of the "Artemis Mission Control" collection, do two things. 1. Add an afterResponse script to that request. It must console.log a text mission dashboard: callsign, mission phase, completion percentage as a progress bar, each of the 5 mission steps with a done or not-done mark, and the log counts. Guard against missing fields. 2. Generate a self-contained mission-dashboard.html in the repo root from the GET /mission JSON response: card-style layout, inline CSS only, the sigil SVG from the response rendered inline, and no external assets. Build it from a real response by sending the request. Authenticate by sending the x-api-key header explicitly set to {{apiKey}} from the artemis.local environment (a vault-linked secret the Postman CLI resolves itself), overriding the empty x-api-key header saved in the requests. Never print the key or write it into a file.

Env-var path (Free accounts)

text
On the "Get mission overview" request of the "Artemis Mission Control" collection, do two things. 1. Add an afterResponse script to that request. It must console.log a text mission dashboard: callsign, mission phase, completion percentage as a progress bar, each of the 5 mission steps with a done or not-done mark, and the log counts. Guard against missing fields. 2. Generate a self-contained mission-dashboard.html in the repo root from the GET /mission JSON response: card-style layout, inline CSS only, the sigil SVG from the response rendered inline, and no external assets. Build it from a real response by sending the request. Authenticate by sending the x-api-key header explicitly set to the ARTEMIS_API_KEY environment variable, overriding the empty x-api-key header saved in the requests. Never print the key or write it into a file.
  1. Ask your agent to run the request again and show you the script output:

Vault path

text
Run the "Get mission overview" request again, show me the Script Logs section of the output, then publish my work to my Postman workspace so the script reaches the cloud. Authenticate by sending the x-api-key header explicitly set to {{apiKey}} from the artemis.local environment (a vault-linked secret the Postman CLI resolves itself), overriding the empty x-api-key header saved in the requests. Never print the key or write it into a file.

Env-var path (Free accounts)

text
Run the "Get mission overview" request again, show me the Script Logs section of the output, then publish my work to my Postman workspace so the script reaches the cloud. Authenticate by sending the x-api-key header explicitly set to the ARTEMIS_API_KEY environment variable, overriding the empty x-api-key header saved in the requests. Never print the key or write it into a file.

Your text dashboard is in the Script Logs.

  1. Open mission-dashboard.html in your browser (open mission-dashboard.html on macOS, xdg-open mission-dashboard.html on Linux, start mission-dashboard.html on Windows).
Tip: Results vary since LLM outputs differ. Tell your agent what to fix, for example "Make the sigil bigger" or "Add a progress percentage", then ask it to run the request again.
4

Mission Log Blitz

Create three mission logs. Category diversity drives mission progression, so each log uses a different category. Your agent creates them from the collection, one request per log.

Key path

Send this prompt. Expect 201 Created for each log:

Vault path

text
Create three mission logs with the Create a mission log request, one in each of these categories: navigation (crew wiseman, phase pre-launch), life-support (crew koch, phase launch) and communication (crew glover, phase transit). Write a realistic title and description for each. Show me the status code and the log id of each log you created. Authenticate by sending the x-api-key header explicitly set to {{apiKey}} from the artemis.local environment (a vault-linked secret the Postman CLI resolves itself), overriding the empty x-api-key header saved in the requests. Never print the key or write it into a file.

Env-var path (Free accounts)

text
Create three mission logs with the Create a mission log request, one in each of these categories: navigation (crew wiseman, phase pre-launch), life-support (crew koch, phase launch) and communication (crew glover, phase transit). Write a realistic title and description for each. Show me the status code and the log id of each log you created. Authenticate by sending the x-api-key header explicitly set to the ARTEMIS_API_KEY environment variable, overriding the empty x-api-key header saved in the requests. Never print the key or write it into a file.

Allowed field values

FieldAllowed values
phasepre-launch, launch, transit, lunar-approach, orbit
categorynavigation, life-support, communication, science, anomaly, crew-status
crew_memberwiseman, glover, koch, hansen
Note: Logs with category anomaly cannot be deleted, only updated. Avoid anomaly for logs you plan to delete later.

To validate: Paste the api_key you got at registration (the same one you stored in the previous step) below. This is a training API key, used once per browser session to validate later steps too, and not stored on the server.