Control what AI does
next, at runtime.
NeoSyntropy is a runtime engine that controls language models through finite state machines. Every action follows a path you define—your business logic is enforced by the engine, not left to a prompt.
Unstructured input. A defined output.
Refund $40 for order ORD-204. The item arrived damaged.
{ "order_id": "ORD-204", "amount": 40, "reason": "damaged", "confidence": 0.96, "out_of_distribution": false }OOD CHECK · PASS
Illustrative decoded output. Your application can reject low-confidence or out-of-distribution results before they continue.
/api/v1/schemaYOUR TASK. DEFINED BOUNDARIES.01 / ACCESS LAYER
One intelligence layer.
Three ways in.
Start with a single API call, compose a workflow, or connect the agent you already run.
NeoSyntropy API
Schema output. Reasoning steps. Routing decisions. Call the capability you need directly over HTTP.
Explore the APINeoSyntropy Framework
Build with typed AI nodes. Connect reasoning, tools, and routing inside a graph you define.
Build a workflowNeoSyntropy Proxy
Send model calls from existing agents through one gateway. Keep your runtime and centralize provider access.
Connect your agent01A / INPUT TOKEN PRICING
Pay for input tokens.
Not model size.
You pay for the input tokens sent to NeoSyntropy. A model’s parameter count describes its capacity—it does not change your usage bill.
See full pricing ↗01B / API INPUT PRICING
Intelligence at
production scale.
NeoSyntropy API input pricing starts at $0.10 per million tokens. The comparison below is a simple input-cost illustration; provider prices and model availability can change.
| Model path | Input cost | Relative to NeoSyntropy |
|---|---|---|
| NeoSyntropy API | $0.10 | 1× |
| GPT-5.6 Luna | $0.20 | 2× |
| Claude Haiku 4.5 | $1.00 | 10× |
| GPT-5.6 Terra | $2.00 | 20× |
| Claude Sonnet 5 | $10.00 | 100× |
02 / INTELLIGENCE PRIMITIVES
A defined job.
An intelligent node.
Give language
a structure.
Extract fields from messages and documents against a schema your application defines.
Explore schema output ↗Give reasoning
a responsibility.
Supply context and permitted tools. Inspect the result of each step before the workflow continues.
Explore reasoning steps ↗Give decisions
a destination.
Let AI choose among defined candidates. Add deterministic rules where the policy must be exact.
Explore routing ↗03 / THE EXECUTION LAYER
You define the map.
The runtime
checks the path.
Models propose. Your graph defines allowed transitions. Schemas, guards, and execution traces make each step inspectable.
Inside the framework ↗BUILD SOMETHING THAT WORKS.
Your next AI system
starts with one node.
Connecting an existing agent? Meet NeoSyntropy Proxy →