The breadboardhub API for your app
Check, simulate and design electronic circuits and Verilog chips from any app over plain HTTPS, including apps made in AI app builders such as Replit, Lovable, Bolt and v0. Every circuit comes back with a link that opens it running live in the browser, and designs come with the parts to buy.
1. Get a token
Create an API token in Settings, API tokens (a free account is enough). It starts with bbh_ and is shown once. Send it on every request:
2. Call an endpoint
Every endpoint takes a JSON body and answers JSON. Circuits use the CircuitJS text format; anywhere a circuit goes, a breadboardhub /sim link works too.
| Endpoint | What it does | Cost |
|---|---|---|
POST /api/v1/circuits/check | Check a circuit | Free |
POST /api/v1/circuits/simulate | Simulate a circuit | Simulation limit |
POST /api/v1/circuits/design | Design a circuit | Design limit |
POST /api/v1/circuits/edit | Change a circuit | Design limit |
POST /api/v1/chips/design | Design a digital chip in Verilog | Design limit |
POST /api/v1/calculate | Run an electronics calculator | Free |
The free endpoints work without a token too. The full schema of every request and answer is in the OpenAPI spec, which many builders and API tools can import: https://www.breadboardhub.com/api/v1/openapi.json.
Answers carry a message (the whole result in plain words, ready to show), the result fields, and sim_url, which opens the circuit running live. Designs and edits also return parts_to_buy, with supplier links that may earn breadboardhub a commission; say so wherever you show them.
Daily limits
| Per token, per day | Free account | Pro account |
|---|---|---|
| Designs, edits and chips | 10 | 50 |
| Simulations | 100 | 300 |
Limits reset at 00:00 UTC and are shared with the MCP server: a token has one allowance however it is used. Costly answers include usage with what is left today. Checking circuits and the calculators are free.
Errors
Errors are JSON { "error": "...", "code": "..." }. Branch on code; show error.
- 400
invalid_json,invalid_input: the body is wrong; a circuit that is not accepted lands here too. - 401
missing_token,invalid_token: no token, or it was revoked. - 429
daily_limit: the token's allowance is used up. The answer hasreset_atand, on a free account,upgrade_urlfor Pro.rate_limited: too many requests a minute. - 422
not_completed: it ran but nothing usable came back. Try again or reword the request. - 503
busy(retry in a few seconds),platform_budget(breadboardhub's daily budget for everyone is spent),unavailable.
Examples
curl
Lovable or any Supabase app: an edge function
The function holds the token; the app calls the function, never breadboardhub directly.
Replit (Node)
Replit (Python)
Next.js (v0, Bolt or your own): a server route
Designs can take up to two minutes, so give the route enough time. Set BREADBOARDHUB_TOKEN in your host's environment variables.
Worked example: ESP32 weather station app with verified wiring
Say your app helps someone build a weather station. One server function designs the wiring, runs it in the simulator and hands back everything the person needs: a live circuit to look at, the sketch to flash and the parts to order.
What "verified" means here: the design passed breadboardhub's structural checks and the simulator ran the circuit and found no faults (no short circuit, nothing over its rating, power reaching every part). The simulator checks the electrical side; it does not run the ESP32's firmware, and it is not a guarantee for a physical build, since real parts have tolerances the simulator does not model. Show the person the sim_url so they can see the circuit for themselves. To change the design, send the circuit to /api/v1/circuits/edit with what to change, then simulate it again.
Or connect over MCP
The same tools are available as a Model Context Protocol server. If the tool you build with lets you connect remote MCP servers, you can add this address instead of calling the REST API; check its documentation for whether it does and how:
Setup for Claude, Cursor and VS Code is on the MCP page. Send the same API token as an Authorization header to use your own limits.
Your data
Descriptions and change requests you send to design or edit are processed by Anthropic to produce the result, and we store them with the result, linked to your token's account. Circuits you only check or simulate are not stored. Details are in our Privacy Policy. Questions: contact us.