Lesson #8
The Builder's Toolkit: Hooks, Plugins, APIs & SDKs
- 1
Webhook
Category: Infrastructure“WEB-hook”
An automatic message one app sends to another the moment something happens, so nobody has to keep checking for updates.
Think of it like… A doorbell. Instead of you walking to the door every minute, the bell tells you the second someone arrives.
Construction: When an inspector marks a permit approved, a webhook tells the scheduling AI to move the crew in the next day.
Business: A signed contract in the e-sign tool fires a webhook that starts invoicing and onboarding automatically.
Why this matters: Webhooks are how separate tools act like one system, which is what makes real-time automation possible.
Open full entry → - 2
Hook
Category: Infrastructure“HOOK”
A spot in a program that is left open on purpose so extra code can run before, during, or after a step.
Think of it like… A stud in the wall with a hanger already on it — you can hang something there without tearing the wall open.
Construction: A hook in the estimating tool runs a safety-margin check every time a bid total is calculated.
Business: A hook fires after every new customer record is saved, adding them to the welcome email sequence.
Why this matters: Hooks let you customize software without rewriting it, so upgrades don't erase your changes.
Open full entry → - 3
Plugin
Category: Infrastructure“PLUG-in”
An add-on you install to give a program a new ability it did not ship with, without changing the program itself.
Think of it like… A drill attachment. Same drill, new job, and you can swap it out any time.
Construction: A takeoff plugin added to the estimating software so it can read measurements straight off a PDF plan.
Business: A tax plugin added to the checkout system so the right rate is applied in every state.
Why this matters: Plugins let a business add exactly the capabilities it needs and skip the ones it doesn't pay for.
Open full entry → - 4
REST API
Category: Infrastructure“REST A-P-I”
A common, predictable way for programs to ask each other for information or to make a change, using plain web addresses.
Think of it like… A restaurant menu with numbered items. Everyone orders the same way, so the kitchen always understands.
Construction: The job-costing app asks the supplier's REST API for current lumber prices before printing an estimate.
Business: A dashboard pulls yesterday's sales from the accounting system through its REST API every morning.
Why this matters: Most business software talks through REST, so knowing the term tells you whether two tools can connect at all.
Open full entry → - 5
API Endpoint
Category: Infrastructure“A-P-I END-point”
One specific address in an API that does one specific job, like listing customers or creating an invoice.
Think of it like… A single window at the DMV. The building is the API; the window handles one kind of request.
Construction: A '/jobs' endpoint returns open jobs, while a '/jobs/close' endpoint marks one complete.
Business: The billing endpoint creates invoices; the reporting endpoint only reads totals and can never change them.
Why this matters: Endpoints are where permissions live, so knowing them is how you control what an AI agent may touch.
Open full entry → - 6
SDK (Software Development Kit)
Category: Infrastructure“S-D-K”
A ready-made bundle of code, tools, and instructions that makes it much faster to build on top of somebody else's system.
Think of it like… A framing kit delivered to the site: lumber cut, hardware sorted, instructions in the box.
Construction: A vendor SDK lets the field app read equipment sensor data without anyone learning the sensor's raw format.
Business: A team adds AI chat to its portal in days using the model provider's SDK instead of writing everything by hand.
Why this matters: An SDK turns months of integration work into days, which decides whether a project is affordable.
Open full entry → - 7
API Key
Category: Infrastructure“A-P-I KEE”
A secret string of characters that proves which account is making a request, so a service knows who to trust and bill.
Think of it like… A job-site badge. It doesn't say your name out loud, but the gate knows exactly who it belongs to.
Construction: The scheduling AI holds a key for the supplier portal so it can check delivery dates on its own.
Business: Each department gets its own key, so if one leaks you can shut that one off without breaking everything else.
Why this matters: A leaked key is the same as a leaked password — most AI security incidents start with one sitting somewhere public.
Open full entry → - 8
Rate Limit
Category: Infrastructure“RAYT LIM-it”
A cap on how many requests you may send to a service in a set time, so no single user can overload it.
Think of it like… A metered on-ramp to the highway. Cars still get on, just a few at a time so traffic keeps moving.
Construction: The pricing agent may check supplier prices 100 times an hour, so it batches its questions instead of asking constantly.
Business: A nightly export is split into chunks because the accounting API allows only 1,000 records per minute.
Why this matters: Agents can fire thousands of requests without blinking, and hitting a rate limit silently breaks automations.
Open full entry → - 9
UI Component
Category: Infrastructure“U-I kom-POH-nent”
One reusable piece of a screen — a button, a card, a form field — built once and used everywhere.
Think of it like… A pre-hung door. Build it once in the shop, then install the same one in every room.
Construction: A 'job card' component shows address, crew, and status the same way on the dashboard, the phone app, and the printout.
Business: Changing the approve button in one component instantly updates it across forty screens.
Why this matters: Components keep a product consistent and cheap to change, which is why redesigns don't take a year.
Open full entry → - 10
Design System
Category: Infrastructure“di-ZINE SIS-tem”
The shared rulebook of colors, type, spacing, and components that keeps every screen of a product looking like one product.
Think of it like… A set of architectural standards for a subdivision — every house is different, but they clearly belong together.
Construction: Field app, office dashboard, and customer portal all use one system, so a crew lead can move between them without retraining.
Business: A design system cuts the time to launch a new internal tool because the parts already exist and are approved.
Why this matters: Consistency is trust: mismatched screens make customers doubt the whole product, and cost teams time reinventing basics.
Open full entry →