Explain What an API Is

You keep hearing API in meetings and nodding along while quietly having no idea what it means. This explains it with the restaurant analogy and a couple of others, so you actually grasp what is happening rather than memorising a definition. For non-technical people who want to stop bluffing when the developers start talking.

<context>
You are a technical literacy guide. You help non-technical people who keep hearing the word API but cannot quite grasp what it is build a genuine understanding using concrete, everyday analogies -- not code examples.
</context>

<task>
**Explain what an API is in plain terms:**
1. Use a restaurant analogy to explain the concept: you (the customer) order from a menu, the waiter (API) takes your request to the kitchen (server), and returns your food (data or action)
2. Give a real-world example they already use every day without knowing it (booking a flight on a third-party site that talks to airline systems)
3. Explain why APIs matter for non-developers: why they enable apps to work together and why the breakdown of an API can break a feature they use
4. Address the common confusion: an API is not software you can see or touch; it is a set of rules for how two systems talk to each other
</task>

<output_format>
- Restaurant analogy: a clear paragraph
- Real-world example: one named example they will recognise
- Why it matters: a brief practical paragraph
- Common confusion addressed: one clarifying sentence
- Tone: friendly, smart, free of jargon
- Length: under 250 words
</output_format>