5A — Verify API Health

1. Find the Health Check request in your collection
2. Click Send — expect a 200 OK response

For mission context, check out the Artemis story.

5B — Register as Crew Member

1. Open Register Crew Member (POST /register)
2. Go to the Body tab and enter:

{
  "name": "Your Name",
  "email": "your.email@example.com"
}

3. Click Send — the response includes your callsign, API key, and sigil (SVG badge)

Tip: Use your real email — {{$randomEmail}} creates a new user every time. Re-sending with the same email returns your existing API key.

Important: After receiving your API key, save it to the apiKey variable in your environment and click Share/Persist All.

1. Stay on the Register Crew Member request
2. Start a new chat in Agent Mode
3. Drag and drop the Register request into the chat
4. Enter this prompt:

5. Re-send the Register request to trigger the script
6. Open the Environment panel — apiKey should now be populated
7. Test it: open Get Mission Overview (GET /mission) → Send → expect 200 OK

Troubleshooting 401 errors:

• Verify apiKey has a value in the environment
• Confirm the request header uses x-api-key: {{apiKey}}
• Make sure the environment is selected in the top-right dropdown

Important: Click Share/Persist All after the script populates the value.

1. Stay on Get Mission Overview (GET /mission)
2. Open Agent Mode and drag the request into the chat
3. Enter this prompt:

4. Send the request again
5. In the response panel, click the Visualize tab to see your dashboard

Tip: Results vary since LLM outputs differ. Tell Agent Mode what to fix — e.g. "Make the sigil bigger" or "Add a progress percentage."

Create 3 mission logs using POST /logs (in the Logs folder → Create Mission Log). Each log needs title, description, phase, category, and crew_member.

Log 1/3 — Navigation Check:

{
  "title": "Pre-flight navigation check complete",
  "description": "All star trackers aligned and verified for lunar transit",
  "phase": "pre-launch",
  "category": "navigation",
  "crew_member": "wiseman"
}

Expect 201 Created — note the log.id in the response for later.

Log 2/3 — Life Support:

{
  "title": "CO2 scrubber maintenance",
  "description": "Replaced CO2 scrubber filter cartridge B. Cabin pressure nominal at 14.7 psi.",
  "phase": "launch",
  "category": "life-support",
  "crew_member": "koch"
}

Log 3/3 — Deep Space Comms:

{
  "title": "Deep Space Network handoff test",
  "description": "Successfully switched primary comms from TDRS to DSN Madrid station. Signal strength 4.2 dBW.",
  "phase": "transit",
  "category": "communication",
  "crew_member": "glover"
}

Category diversity drives mission progression — you need logs across multiple categories to reach 100%.

Note: Logs with category anomaly cannot be deleted — only updated. Anomalies are permanent mission records.

Full examples: artemis.up.railway.app/guide/logs