Orbit
Open Terminal Apply for Beta
LIVE ON POLYMARKET + HYPERLIQUID

Your AI Trading Copilot

Orbit is the Agent-Native Financial Execution Layer.

Track events, analyse price dislocations, enforce limits, and route orders through one shared system — with you holding the keys.

Open Terminal →Create a Workflow
$ orbit run cross-venue-arb --budget 5000
↳ market filter ✓  risk limit ✓  wallet scope ✓
✓ 5 orders staged · awaiting confirmation
8,142Signals scanned · sample run
6Passed market filters
$3k / $5kDeployed / budget limit
Connected venues
Polymarket•Hyperliquid

01 — The problem

An alert isn’t execution.
A controlled workflow is.

Markets never stop, but every order still needs context, sizing, limits, and a route to the venue. Without one execution layer, those decisions splinter across bots, wallets, and tabs.

01 / INTENTMarket signalNews, price, wallet, funding
02 / ORBITPolicy + executionFilter, size, confirm, route
03 / VENUESigned orderPolymarket or Hyperliquid

02 — The primitive

Three stages stand between a signal and a fill.

Every workflow follows the same path: listen to the market, analyse against your rules, then execute inside the limits you set.

8,142 MARKET SIGNALS
6 PASS YOUR FILTERS
5 ORDERS STAGED
01 / LISTEN

Bring the market into one stream

Watch venue books, funding, news, social signals, and on-chain activity without stitching together separate monitors.

02 / ANALYSE

Turn conditions into a strategy

Apply expected-value thresholds, sizing logic, risk gates, and confirmation rules to the same shared context.

03 / EXECUTE

Route the order, keep the keys

Send signed orders through an agent wallet with a revocable budget scope and a traceable execution history.

FRAGMENTED EXECUTION
signal → switch tools → size manually
→ open wallet → place order
ORBIT WORKFLOW
listen → analyse → risk gate
→ confirm → execute → record

03 — The developer surface

One execution layer behind every interface.

Chat, workflow, API, MCP, CLI, and partner apps all call the same strategy logic, wallet scopes, and venue adapters.

REQUESTPOST /v1/workflows/run
{
  "strategy": "cross-venue-arb:v3",
  "venues": ["polymarket", "hyperliquid"],
  "budget": 5000,
  "confirm": "human"
}
RESPONSE200 · STAGED
{
  "status": "awaiting_confirm",
  "checks": { "risk": "pass", "budget": "pass" },
  "orders": 5,
  "audit": "ipfs://Qm4f…9c2"
}
Built with
Orbit APIMCPCLISDK
Create Workflow →Open Terminal

04 — Where Orbit works

One agent. Three operating modes.

ASK ORBIT · WORKFLOW DRAFTSTEP 1/4
ORBITFirst, what should wake this workflow?

Build a workflow in conversation

Orbit asks for the source, trigger, and risk limits, then stages a draft for review.

OPEN ASK ORBIT →
AUTONOMOUS WORKFLOWRUNNING
FUNDINGrate < 0
RISK GATEcap $5k
VENUElimit order
Agent wallet budget$3,000 / $5,000

Run inside fixed limits

Let the workflow act continuously while risk, budget, and venue rules stay enforced.

BUILD A WORKFLOW →
STRATEGY LIBRARYPUBLISHED
Cross-Venue ArbitrageV4
SIGNALCombined ask < 98¢
LIMITS$500/order · 6 max
Updated 18m agoDEFINITION ONLY

Version and share the definition

Publish strategy logic without sharing funds, positions, credentials, or private run data.

VIEW STRATEGY →

05 — Where Orbit sits

For agents, execution becomes a shared infrastructure layer.

Orbit sits between agent intent and venue execution — turning market context into bounded, reviewable actions.

MANUAL TRADING · FOR REFERENCE
Humandecides and sizes
↓ instructs
Trading interfaceplaces the order
↓ routes
Venueresolves the market
AGENT-NATIVE EXECUTION
Human or autonomous agentexpresses intent
↓ instructs
Chat · Workflow · API · MCP · CLIshared interfaces
↓ calls
OrbitListen × Analyse × Execute
↓ controls and routes
Agent Wallet + Venue Adaptersnon-custodial execution rails
PolymarketHyperliquidIPFS Audit

06 — Security & assurance

Built to keep authority with you.

NON-CUSTODIAL

Your keys stay in your wallet

Orbit scopes what the agent wallet may do; it does not take custody of your main wallet or venue credentials.

Manage Venue Connections →
RISK GATE

Limits are checked before routing

Budget, position sizing, venue, and confirmation rules sit in the execution path — not in a note beside it.

Inspect Workflow Rules →
AUDIT HISTORY

Every decision leaves a trace

Workflow versions, confirmations, orders, and fill events are recorded with an IPFS audit hash.

View Account Activity →

07 — Go deeper

Start from the surface you need.

Browse Community →
PRODUCT›_

Ask Orbit

Turn a market question into a reviewable strategy and staged execution.

 BUILDER◇

Workflow Builder

Connect a source, threshold, action, risk gate, and venue route.

 LIBRARY↗

Community Strategies

Study a creator’s published definition, then fork it into a private v1 draft.

08 — FAQ

Common questions.

What is an agent-native financial execution layer?

It is the shared layer between an agent’s intent and a venue order. Orbit brings market inputs, strategy logic, risk gates, confirmation, wallet scope, routing, and execution history into one path.

Does Orbit hold my funds or private keys?

No. Orbit uses a budget-scoped, revocable agent wallet while your main wallet remains under your control.

Can a workflow run without asking every time?

Yes, when you configure autonomous confirmation rules. Chat mode can still stop every order for manual confirmation.

Which venues are connected?

Polymarket and Hyperliquid are the current connected venues in this prototype.

What gets shared when I publish a Strategy?

The versioned strategy definition only. Funds, positions, budget amounts, credentials, and private run history are never part of the published object.

The market is already continuous. Your execution layer should be too.

Build the workflow, backtest it on recorded venue history, and keep every order inside your limits.

Open Terminal →Create a Workflow