1. Sign in or sign up at postman.com.
2. Create a new Blank Workspace.
3. Name it: Artemis II - [your name]

1. Click the + icon → Import.
2. Paste this URL and click Import:

https://raw.githubusercontent.com/mishra-aanchal/artemis-mission-control-api-workshop/refs/heads/main/openapi.yaml

3. Postman auto-generates a collection from the spec.

1. Open Agent Mode (the AI chat panel in Postman).
2. Use this prompt:

Create an environment called artemis.local with variables - baseUrl, apiKey and logId.

1. Click on the artemis.local environment.
2. Set baseUrl to:

https://artemis.up.railway.app

3. Mark apiKey as secret (so it's hidden when screen-sharing).

5A — Verify the API is Running

1. Open the Health Check request in the collection.
2. Click Send.
3. Expect a 200 OK response.

5B — Register as Crew Member

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

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

3. Click Send.
4. You'll receive your callsign, API key, and sigil (SVG badge).

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

Generate a script to save the api key from response to the environment variable apiKey

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

1. Stay on Get Mission Overview.
2. Open Agent Mode, drag the request into the chat.
3. Enter this prompt:

Create a card-style visualisation by rendering the SVG as HTML rather than an image. Keep all the fields in the card. Make it like a mission dashboard;

4. Send the request again.
5. In the response panel, click the Visualize tab.

Part A — Start Documentation (Background)

1. Open Agent Mode (new chat).
2. Drag and drop your entire collection into the chat.
3. Enter this prompt:

Add documentation for this collection. Refer to the spec for specific examples

4. Let it run — do not wait for it to finish. Move on to Part B immediately.

Part B — Mission Log Blitz: Create 3 Logs

You need 3 mission logs with different categories to advance your mission. Send them one by one using POST /logs.

1. Go to the Logs folder in your collection.
2. Open Create Mission Log (POST /logs).
3. Work through each log below.

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

{
  "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"
}

{
  "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"
}

Part A Check-In — Documentation Done?

Head back to your Agent Mode chat. If docs are done, browse your collection and check that requests now have descriptions and example payloads.

You've created 3 logs. Now finish the remaining mission requirements.

6A — Update a Log

1. List your logs: send GET /logs to see all your entries.
2. Pick a log ID (or use the one from Log 1).
3. Open Update Mission Log (PATCH /logs/:id).
4. Replace :id in the URL with your actual log ID.
5. Set the body:

{
  "title": "Pre-flight navigation check complete — VERIFIED BY FLIGHT DIRECTOR",
  "description": "All star trackers aligned. Secondary backup nav confirmed. Ready for TLI burn."
}

6. Click Send — expect 200 OK.

6B — Delete a Log

1. Delete one of the logs you created using the log ID from a previous request.
2. Open Delete Mission Log (DELETE /logs/:id).
3. Replace :id in the URL with your actual log ID.
4. Click Send — expect 200 OK.

6C — Request a Mission Briefing

1. Open POST /mission/brief.
2. Set the body to:

{}

3. Click Send — expect a briefing response summarizing your mission status.

6D — Verify Splashdown 🎯

1. Open GET /mission and click Send.
2. Look for completion_percentage: 100 and all steps showing completed: true.

1. Start a new chat in Agent Mode.
2. Drag and drop your collection into the chat.
3. Enter this prompt:

Generate a new collection to do an end-to-end integration test

- Refer to example responses for data to be sent in the body.
- Refer to the collection attached for the request type and add scripts
  to chain data between the requests.
- Create an environment "artemis.test" (baseUrl: https://artemis.up.railway.app)

Flow:
1. Register crew member (POST /register) — save api_key & callsign
2. Generate Mission Briefing (POST /mission/brief) with phase: transit
3. Get Mission Overview (GET /mission)
4. Create 3 mission logs (POST /logs) — save each log ID (path is response.log.id)
   Crew: wiseman, glover, koch, hansen
   Category: navigation, life-support, communication, science, crew-status, anomaly
5. Update one log (PATCH /logs/{logId1}) — category to science
6. Delete communication log (DELETE /logs/{logId2})
7. Generate final briefing (POST /mission/brief) with empty body
8. Verify mission completion (GET /mission) — all steps completed: true

Do not write tests yet — we will add them subsequently.

4. Run the collection using the Collection Runner — verify green checkmarks.
5. Then, in the same chat, enter:

Run the collection using the collection runner and add integration tests based on the responses.

Setup

1. Install Postman's official MCP server in your AI tool (Claude Desktop, etc.).
2. Generate a Postman API key at: go.postman.co/settings/me/api-keys
3. Add the key to your MCP server configuration.

Try It — Send This to Claude

Check the Artemis leaderboard from my Postman collection id - <your collection id>
and tell me status of all participants progress.

More MCP Commands to Try