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.
- 1Launch
- 2Orbit
- 3Transit
- 4Flyby
- 5Return
- 6Splashdown
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.
- Send this prompt. Your name and email are prefilled from your profile; click them to edit:
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.
- The registration response holds your
callsign, yourapi_keyand asigil(an SVG badge). Paste theapi_keyinto 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.
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.
Option A — Vault (Solo, Team and Enterprise plans)
- 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.
postman secret create ARTEMIS_API_KEY --terminalpostman secret create ARTEMIS_API_KEY --terminal- Ask your agent to link the secret to the environment variable. It never sees the value:
-
Check the YAML:
apiKeyshould hold secret and vault ids, not your key. -
Check it works with this prompt. Expect
200 OKwith your callsign and mission status:
Option B — Env var (Free plans)
- 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.
read -s ARTEMIS_API_KEY && export ARTEMIS_API_KEYread -s ARTEMIS_API_KEY && export ARTEMIS_API_KEYOn Windows PowerShell, use $env:ARTEMIS_API_KEY = "<your key>" instead.
-
Leave
apiKeyempty in the environment file. There is nothing more to push. -
Check it works with the same prompt as above (start your agent from this terminal). Expect
200 OKwith your callsign and mission status:
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.
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.
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.
- Send this prompt to your agent:
Vault path
Env-var path (Free accounts)
- Ask your agent to run the request again and show you the script output:
Vault path
Env-var path (Free accounts)
Your text dashboard is in the Script Logs.
- Open
mission-dashboard.htmlin your browser (open mission-dashboard.htmlon macOS,xdg-open mission-dashboard.htmlon Linux,start mission-dashboard.htmlon Windows).
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.
Send this prompt. Expect 201 Created for each log:
Vault path
Env-var path (Free accounts)
Allowed field values
| Field | Allowed values |
|---|---|
phase | pre-launch, launch, transit, lunar-approach, orbit |
category | navigation, life-support, communication, science, anomaly, crew-status |
crew_member | wiseman, glover, koch, hansen |
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.