You do not need to become a programmer to understand the language around your product. Watch the moving part in each demo. It shows the basic job the term is doing.
An API is a way for one product to ask another product or service for something and get an answer back.
Why it matters: Your product can use powerful outside services instead of building every ability itself.
Example: Your app asks a weather service for the current temperature.
Think of it like a bridge: your app sends a request across, and the answer comes back across the same bridge.
An API key is a private code that identifies your product and gives it permission to use an API.
Why it matters: Services use keys to control who can use them and to track that use.
Example: Your product sends its private key before a service accepts its request.
Think of a house key: the right API key unlocks the door; without it, the request stays outside.
A webhook lets one service automatically tell another service that something just happened.
Why it matters: Your product can react immediately without constantly asking, “Did anything change?”
Example: A payment service tells your app the moment a customer pays.
The event pushes the news automatically.
An endpoint is a specific API address used for a specific job.
Why it matters: Different API jobs can have different destinations.
Example: A weather API may have one endpoint for current weather and another for forecasts.
The request goes to the address for the job.
A database is the organized place where a product remembers information.
Why it matters: Without stored data, your product cannot reliably remember users, messages, orders, settings, or progress.
Example: A member profile is saved today and loaded again tomorrow.
Think of an organized filing cabinet: save information in the right drawer, then pull it back out when you need it.
Authentication is the process of proving who a user is.
Why it matters: Your product needs to know which person is signing in before showing private account information or allowing protected actions.
Example: A user signs in and the product recognizes their account.
Identity is checked before access opens.
The front end is what the user sees and uses. The back end is the behind-the-scenes part that handles data, rules, accounts, and other hidden work.
Why it matters: Most real products need the visible experience and the hidden system to work together.
Example: A user presses Save on the front end; the back end stores the information.
Think storefront and back room: the front end is what the customer uses; the back end does the hidden work.
An environment variable is a separate place for configuration values—often private values—so they do not have to be written directly into public product code.
Why it matters: It helps keep secrets such as private API keys out of places users can see.
Example: Your app reads an API key from its secure environment when it needs it.
Think of a locked note in the back office: the app can use the secret without putting it in the public window.
JSON is a common way of organizing information so products and APIs can send data to each other in a predictable structure.
Why it matters: You will often see JSON when AI is working with APIs, product data, or configuration.
Example: A service sends back a name, city, and temperature as organized fields.
{"name": "Mike","city": "Detroit","temp": 72}
Loose values become named, organized data.
A schema is the plan for how information is organized—what fields exist, what kind of information belongs in them, and how pieces relate.
Why it matters: A clear structure keeps product data consistent and easier to use.
Example: A Customers table may have a place for name, email, and account ID.
The plan tells each piece of data where it belongs.
Hosting is the service that keeps your website or web product online so other people can reach it.
Why it matters: A product sitting only on your computer is not available to the public.
Example: Your finished site is placed on a host and receives a live web address.
The host keeps the product online and reachable.
Deployment is the act of putting a new or updated version of your product onto its live host.
Why it matters: Building a change is not the same as putting that change live for users.
Example: Version 2 is deployed and replaces Version 1 on the live site.
The new build moves from finished to live.
A repository is a place where product files and their change history can be stored and managed.
Why it matters: It gives a project an organized home and makes it easier to track what changed.
Example: A project is stored on GitHub with a history of saved changes.
Files and saved changes stay together.
An SDK is a package of tools a company provides to make it easier to use its service inside a product.
Why it matters: AI may use an SDK to connect a service faster instead of rebuilding common connection work from scratch.
Example: A service provides ready tools for sign-in, file uploads, or payments.
Think of a toolbox: an SDK gives you ready-made tools so you do not have to build every common piece from scratch.
Supabase is a service that gives your product a database, user accounts, file storage, and other behind-the-scenes tools.
Why it matters: It can give a real product several important back-end abilities in one place.
Example: Your app signs in a user, saves their profile, and stores an uploaded image through Supabase.
One service powers several back-end jobs.
A token is a digital piece of information used to prove identity, permission, or access for a period of time.
Why it matters: Products can use tokens so a user or service does not have to send a password with every request.
Example: After sign-in, a token travels with a request and the protected service allows access.
Think of a wristband after check-in: the token travels with you as proof that you already have permission.
When one of these terms appears while you are building, come back here, read the definition, and watch the demo again. Understanding what the word does is more important than memorizing technical vocabulary.
Continue to Course 10 — Golden Rules for Building With A.I.