hardwareblocks_
IoT for the prompt generation

Vibe code.
Meet hardware.

Your ideas don’t have to stay in a browser.
Give them a camera. A sensor. A button.
Let your code touch the real world.

Get started Or send your agent

Tiny devices. Your logic. AI-first by design.

Concept render of a tiny matte-black sensor pod with a USB-C port, shown beside a USB-C cable for scale
+Small enough to go
where the idea is.
USB-C / compact sensor podConcept render
Developer preview

Docs, recipes, REST + read-only MCP are live.

Hardware connectivity is in development.
~/get-started

Skip the tour.
Start with a prompt.

Copy this into Claude, ChatGPT or your coding agent. Give it an idea. Let it read the docs and scaffold your first build.

hardwareblocks / start.mdAgent-ready
$ copy → paste → build

llms-full.txt ↗catalog.json ↗Read the quickstart ↗No API key needed for the public catalogue.
hardware / software

Small box.
Big “what if”.

Choose a physical input. Pair the device. Build its behaviour with AI. The concept brings compatible electronics, an enclosure and power into a kit you assemble — or receive assembled.

Camera. Motion. Distance. Button. Your application decides what comes next. Start with a simulated event today; connect real hardware as the platform develops.

◉ Camera⌁ Motion↔ Distance⊙ Button
~/recipes

Pick a side quest.

Same idea: a physical event becomes software.
Four starting points. Fork the behaviour.

bike.tsIllustrative logic

If it moves, your code knows.

A motion event from your bike. An alert defined by you.

Bluetooth → phone / gateway → your app
on('bike.motion', (event) => {
  if (event.armed)
    notify('Your bike just moved.');
});
Simulated input
{
  "source": "simulation",
  "type": "bike.motion",
  "armed": true,
  "motion_detected": true
}

Waiting for an example event.

Recipe JSON ↗
Parts + build notes
Motion sensor, battery, enclosure and bike mount. Bluetooth needs a nearby phone or gateway; remote notifications also need internet access. This is not GPS tracking.
~/connect

Less browsing.
More building.

Your agent can read the same source you do.
Public endpoints. Structured recipes. No scraping required.

{ }REST APILive / read-only

Fetch your next build.

Get the catalogue, a recipe or a simulated event. No SDK to install.

GET /api/catalog
Open JSON ↗
⌘MCP serverLive / read-only

Give your agent the context.

Discover blocks, inspect recipes and get starting prompts through MCP.

https://hardwareblocks.com/mcp
Connection details ↗

These endpoints expose build knowledge and examples. Device pairing, live telemetry and device control are still in development.

Still using websites?

No judgement. We made this one for your agent, too.

curl -fsSL https://hardwareblocks.com/llms.txt
Copy prompt. Close tab.