Think of the internet as full of tiny kitchens (servers) that will cook up data for you. You don't walk in and start cooking β you read their menu (the API) and order. Tap a dish below to send your order. π
π The menu β 4 things you can order
Each one is an API endpoint: a single thing this kitchen knows how to make.
Your order
π½οΈ
Pick a dish from the menu above to place your order.
π΄ The restaurant, decoded
π
You = the customer. You decide what to ask for.
π
The API = the menu. The list of things you're allowed to order.
π³
The server = the kitchen. It looks up your order and makes it.
π½οΈ
JSON = your food. The data, served in a tidy, labeled format.
GET only ASKS β it just fetches a copy of the data. It never changes, deletes, or breaks anything in the kitchen. Totally safe to try. π
π One more thing. Some menus need a key β an API key is like a password that proves you're allowed to order. NEVER paste a real API key into a public GitHub repo. Bots scan the internet for leaked keys within minutes and will run up your bill. Keep keys secret. π€«
Here's the big idea.
An API is a menu of things one computer will fetch for another. You send a GET request β that's just politely asking, "please get me this" β and it replies with JSON:
a tidy, labeled format that every programming language reads the exact same way.
{ } is an object (a labeled box of key:value pairs), [ ] is a list,
"text" sits in quotes, numbers don't, and answers that are yes/no are true / false.
That's how you teach your AI brand-new skills: let it order from the world's menus. π