Kit

1Everything Here Can Be Done in the Browser

You can do the whole week in the Request Builder, with nothing to download. The only other site you visit is console.groq.com, to create a free key in step 8. Ten steps, in order:

The terminal commands in section 4 and the bridge in section 5 are the same requests again, for when you want them outside the browser. They are optional this week.

2Links

3Aarav's Doors

Base address: __SITE__/aarav. Every reply echoes back the parts the machine read, under you_sent. Every error names the part to fix.

The key goes in a header: Authorization: Bearer aarav_…. The machine checks the parts in the order of the list: address, then action, then key, then package. The first part that fails is the only error you get.

4The Same Requests in a Terminal

Optional. curl sends a request from the terminal and prints the reply. It is already installed on Mac and on Windows 10 and 11.

Read: GET from the echo

Add -i after curl to see the status code and the reply headers as well as the package.

Create: POST to the echo

curl -X POST https://httpbin.org/post \
  -H "Content-Type: application/json" \
  -d '{"text": "I open Jira, read the tickets, write a report, post it on Slack."}'

{"text": "I open Jira, read the tickets, write a report, post it on Slack."}

Your text comes back at json.text in the reply.

Create a key at Aarav's

curl -X POST __SITE__/aarav/keys \
  -H "Content-Type: application/json" \
  -d '{"name": "Riya"}'

{"name": "Riya"}

The reply is 201 with your key. Put it in an environment variable for this terminal session, so it never appears inside a command:

Create a diagnosis

curl -X POST __SITE__/aarav/diagnoses \
  -H "Authorization: Bearer $AARAV_KEY" \
  -H "Content-Type: application/json" \
  -d '{"workflow": "I open Jira, read the week'"'"'s tickets, write a status report and post it on Slack. About 90 minutes."}'

{"workflow": "I open Jira, read the week's tickets, write a status report and post it on Slack. About 90 minutes."}

Run it twice. The same diagnosis comes back both times: this machine follows rules.

Create a reply from Groq

curl https://api.groq.com/openai/v1/chat/completions \
  -H "Authorization: Bearer $GROQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model": "openai/gpt-oss-120b", "messages": [{"role": "user", "content": "I open Jira, read the week'"'"'s tickets, write a status report and post it on Slack. About 90 minutes. Diagnose this workflow: repeated pattern, bottleneck, first AI step."}]}'

{"model": "openai/gpt-oss-120b", "messages": [{"role": "user", "content": "I open Jira, read the week's tickets, write a status report and post it on Slack. About 90 minutes. Diagnose this workflow: repeated pattern, bottleneck, first AI step."}]}

Run it twice. Different words come back each time. The door is deterministic; what comes through it is probabilistic. The text is at choices[0].message.content.

An environment variable set this way lasts until you close the terminal. Do not paste keys into commands you share, and do not post your terminal history.

Every code on demand

5Bridge to Building APIs and the Backend

The Groq call in Python

The same request as the curl command, in Python. In the next lesson this moves inside a FastAPI backend, which is where the key belongs. Install the library once with pip install requests (Mac: pip3), and set GROQ_API_KEY as above before you run it.

import os
import requests
 
response = requests.post(
    "https://api.groq.com/openai/v1/chat/completions",address
    headers={"Authorization": "Bearer " + os.environ["GROQ_API_KEY"]},key
    json={package
        "model": "openai/gpt-oss-120b",package
        "messages": [{"role": "user", "content": "I open Jira, read the week's tickets, write a status report and post it on Slack. Diagnose this workflow."}],package
    },package
)
print(response.status_code)code
print(response.json()["choices"][0]["message"]["content"])reply package

The action is in the function name: requests.post. Passing json= turns the dictionary into JSON and adds Content-Type: application/json for you. os.environ reads the key from the environment, so it never sits in the file.

6Words You Will Meet

Address, action, key, package. Code, package.Companion pages: reading the Network tab · keys · troubleshooting