01
Trigger
Start a run from a manual input, webhook, or supported market signal.
Signal · intelligence · control
Move at the speed of the signal.
Build autonomous market workflows that watch your inputs, call the decision engine, enforce your risk policy, and record every outcome.
Builder livePolicy guardedEvery run recorded
The loop
Signal in. A controlled decision out.
One workflow carries context from the first trigger to a result you can inspect. You design the graph; Peregrine runs the same guarded path every time.
- 02
Context
Bring market data and portfolio context into one structured decision input.
- 03
Decision
Call the selected model and validate its output against a strict trade schema.
- 04
Guard
Apply venue rules, position limits, global policy, and the kill switch.
- 05
Record
Keep the trigger, reasoning, status, and confirmed execution result together.
One graph · explicit contractstrigger → context → decide → guard → record
Two starting points · one loop
Defend the book, or explore new ground.
Use the same visual builder with a different starting point. The contracts, risk checks, and activity trail stay consistent.
Respond to what you hold
Protect a position. Press an advantage.
Start with your current exposure. When a signal changes the case for a market, the workflow adds context and proposes a controlled response.
- Use portfolio context before a decision
- Keep every action inside global risk limits
- Record hold, increase, reduce, and exit outcomes
Sample portfolio trace
Flow previewPosition response
Illustrative run · no live order
12:04:31.2Signal matched an open prediction market
12:04:31.4Portfolio context attached to decision input
12:04:31.7Risk policy checked before venue routing
12:04:32.0Decision recorded: HOLD · no execution
Transparency by default
Nothing important happens off the record.
Peregrine keeps the decision contract, policy checks, and runtime state visible. When execution is not confirmed, the interface says so.
0
Visible stages
From incoming trigger to a recorded result
0
Global policy
One source of truth for limits and venue access
0%
Schema checked
Model decisions must match the shared trade contract
Inspect the run
See the trigger payload, structured decision, status, and any confirmed execution result in Activity.
Control the boundary
Position caps, venue access, and the global kill switch stay visible in one risk policy.
Fail visibly and safely
Missing model access falls back to hold, while API and venue failures remain explicit instead of becoming fake orders.
Decision output is validated before it can reach a venue adapter.
Your next signal is coming
Build the first flow before it arrives.
Connect a trigger, choose the decision path, set your boundaries, and see the complete run in one workspace.