Key Concepts
This page walks you through the core ideas behind Leapter, following the journey from creating your first Blueprint to deploying it in production. Each section links to the detailed documentation where you can learn more.Create
Build a Blueprint with AI, from a template, or from scratch
Edit & Refine
Modify your logic inline or with AI assistance
Test
Run your Blueprint and verify it works correctly
Deploy
Connect via API, export to n8n, embed, or generate code
Blueprints
A Blueprint is the central building block in Leapter. It is a visual, executable representation of your business logic — displayed as a flowchart-like diagram that you can run, test, and deploy. Unlike logic written inside AI prompts, a Blueprint executes deterministically: the same inputs always produce the same outputs. This makes Blueprints reliable enough for billing, compliance, risk calculations, and any other scenario where “close enough” is not acceptable.Projects
A Project is a container that groups related Blueprints together. For example, you might have a project for “Insurance Calculations” that contains Blueprints for premium rating, no-claims bonus logic, and risk assessment. One Blueprint in a project is the active Execution Scope — the entry point that runs when the project is invoked from outside. Its signature is the project’s external interface, exposed to the REST API, MCP, and other integrations. The other Blueprints in the project are reusable sub-routines that the Execution Scope calls via Call nodes. Projects are also the unit of sharing — when you work in a team, all team members can access the team’s projects and the Blueprints inside them. To share a project read-only with someone outside your team, generate a public link.Creating a Blueprint
Leapter gives you three ways to create a Blueprint:- Generate with AI — describe your logic in plain language and Leapter builds the full Blueprint for you. This is the fastest way to get started.
- From Example Template — start from a pre-built example (like a pricing calculator or greeting logic) and customize it.
- From Scratch — create an empty Blueprint and build every node yourself.
The Blueprint Editor
The Blueprint Editor is a single workspace where you build, inspect, and run every Blueprint in your project. The editor opens directly into a structured document — the Specification view — that shows your project’s Type Definitions, Inputs and Outputs, and each Blueprint with its interactive diagram embedded inline. To focus on a single Blueprint, you maximize it in place and the canvas fills with its Diagram view. There is no separate “diagram page” — the diagram view is just one mode of the same editor.Blueprint Elements
Blueprints are made up of different types of nodes, each with a specific purpose. Here is a real Blueprint showing several element types working together — Decision nodes (yellow), Assignment nodes (purple), Call nodes (blue), and Return nodes (green):
| Element | What it does |
|---|---|
| Assignment | Performs calculations and stores results in variables |
| Decision | Creates conditional branches — routes the flow based on true/false conditions |
| Loop | Repeats a section of logic (over items, with a counter, or while a condition is true) |
| Return | Ends execution — either successfully or with an error |
| Call | Calls another Blueprint as a sub-routine, enabling modular, reusable logic |
Editing a Blueprint
Once a Blueprint exists, you can modify it three ways:- Inline Editing — click on any node, description, or heading to edit it in place.
- AI Editing — select a node, press Ctrl+I (Cmd+I on Mac), and describe what you want to change in natural language. AI modifies the logic for you.
- Sync & Suggestions — the descriptions you write and the logic in your diagrams describe the same thing. When they drift apart, the sync buttons in the editor’s right toolbar let AI propose updates so they line up again.
Testing
Before deploying, you can verify your Blueprint works correctly:- Test your Blueprint — run your Blueprint with sample inputs directly in the editor and inspect the outputs step by step.
- Test Suites — create reusable sets of test cases that you can run repeatedly to catch regressions. You can also auto-generate test cases with AI.
Deploying
Once tested, you can connect your Blueprint to the outside world through multiple channels:| Method | Description |
|---|---|
| AI Protocol (MCP) | Connect AI assistants like Claude Desktop or Cursor to your Blueprint using the Model Context Protocol |
| Web API (REST) | Call your Blueprint through a standard REST API from any application |
| n8n Workflows | Export ready-made n8n workflows that call or embed your Blueprint logic |
| Export as Code | View your Blueprint transpiled to JavaScript or Python |
| Embed in Websites | Embed an interactive, read-only Blueprint viewer in any webpage |