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

Update a Mission Log

Update one of the logs you created earlier so the mission records a change.

Key path
  1. Send this prompt to your agent:

Vault path

text
List my mission logs, pick one of them, and update its title and description with the Update a mission log request. Show me the id of the log and the response. 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
List my mission logs, pick one of them, and update its title and description with the Update a mission log request. Show me the id of the log and the response. 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. Expect 200 OK.

To validate: If you already pasted your Artemis training API key on an earlier step, LiftOff reuses it for this check. Otherwise paste your api_key below. Session only, not stored on the server.

2

Delete a Mission Log

Delete one non-anomaly log so the mission records a removal.

Key path
  1. Send this prompt to your agent:

Vault path

text
List my mission logs, pick one that is not in the anomaly category, and delete it with the Delete a mission log request. Tell me the id of the deleted log and the status code. 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
List my mission logs, pick one that is not in the anomaly category, and delete it with the Delete a mission log request. Tell me the id of the deleted log and the status code. 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. Expect 200 OK, then enter the deleted log ID below and validate.

Caution: Logs with category anomaly cannot be deleted, only updated. Choose a non-anomaly log.

To validate: Enter the deleted log ID below. Your Artemis training API key is reused from this browser session if you already entered it, otherwise paste your api_key. Session only, not stored on the server.

3

Request Mission Briefing

Request a briefing that summarizes your mission status, log counts by category, and what to do next.

Key path
  1. Send this prompt to your agent:

Vault path

text
Request a mission briefing with an empty JSON body (POST /mission/brief) and show me the response. 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
Request a mission briefing with an empty JSON body (POST /mission/brief) and show me the response. 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. Read the response. You will receive a briefing with status, category counts, and recommendations.

To validate: If you already pasted your Artemis training API key on an earlier step, LiftOff reuses it for this check. Otherwise paste your api_key below. Session only, not stored on the server.

4

Verify Splashdown

Confirm the mission is complete. Splashdown means completion_percentage is 100.

Key path
  1. Send this prompt to your agent. Because it runs the request from the collection, the dashboard script from the earlier step runs and prints in Script Logs:

Vault path

text
Run the "Get mission overview" request again. Show me the Script Logs output, the completion_percentage, and which mission steps are not completed yet, if any. 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 output, the completion_percentage, and which mission steps are not completed yet, if any. 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. Check for splashdown in either place:

    • Script Logs: your text dashboard shows 100% completion
    • Response JSON: completion_percentage: 100 and all steps showing completed: true
  2. Optional: ask your agent to regenerate mission-dashboard.html from the latest response and open it in your browser.

Vault path

text
Run the "Get mission overview" request again and regenerate mission-dashboard.html in the repo root from the latest response, keeping the same card layout, inline CSS and inline sigil SVG. Then open it in my browser. 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 and regenerate mission-dashboard.html in the repo root from the latest response, keeping the same card layout, inline CSS and inline sigil SVG. Then open it in my browser. 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.

If you see 100%, congratulations, you have achieved splashdown!

If not 100%, check which step is incomplete. You likely need more logs across different categories. Ask your agent for a new briefing for recommendations. It tells you exactly what is missing.

#RequirementRequest
13+ logs createdCreate a mission log
2Update at least one logUpdate a mission log
3Delete a logDelete a mission log
4Get a mission briefingGenerate a mission briefing
5Verify splashdownGet mission overview

To validate: If you already pasted your Artemis training API key on an earlier step, LiftOff reuses it for this check. Otherwise paste your api_key below. Session only, not stored on the server.