
IRL Gateway
io.github.norve-labsv0.3.0Updated Oct 7, 2026
An AI agent's trading mandate it can't break: checked before every order, reasoning sealed in IRL.
Overview
Lets an AI agent place spot market orders through a policy-checked gateway that seals each trade rationale into a tamper-evident trace.
- What it does
- IRL Gateway sits between an AI agent and an exchange account, checking every order against the agent's registered mandate (active status, notional cap, allowed assets and venues) before it reaches the venue. Its main tool, execute_trade, runs authorize, place and bind steps and returns filled, denied, blocked or failed with a trace id. Supporting tools read the mandate and kill-switch state, quotes, balances, a sealed trace, and a local journal of recent trades. Rationales are hashed and sealed into IRL's trace while the plaintext stays in a local journal.
- When to use it
- Use it when an assistant is allowed to trade but should be constrained by a pre-registered mandate and leave a verifiable record of what it was authorized to do, what it said it was doing, and what actually filled. Paper trading mode is a low-risk way to try this without exchange keys.
- Requirements
- Runs locally over stdio, installed from PyPI and started with uvx. Requires IRL_BASE_URL, IRL_AGENT_ID, IRL_MODEL_HASH and the secret IRL_API_TOKEN, plus network access to the IRL server. GATEWAY_BROKER selects paper (default) or exchange; exchange mode additionally needs EXCHANGE_API_KEY and EXCHANGE_API_SECRET. Desktop only.
Installation
In SourceWeft
- Open IRL Gateway in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
IRL Gateway
Give your AI agent a trading account it can't misuse, and a record of every decision it can't rewrite.
IRL Gateway is an MCP server that sits between an AI agent (Claude, ChatGPT, or your own) and an exchange account. Every order the agent places goes through the IRL Engine:
- Policy before execution. IRL checks the order against the agent's mandate (active status, notional cap, allowed assets and venues) before anything reaches the exchange. Out of mandate means no order.
- The rationale is sealed. The agent must say why it is trading. The gateway hashes that rationale together with the trade inputs and seals the hash into IRL's tamper-evident trace, anchored daily to Bitcoin. The plaintext stays in your local journal.
- Intent is reconciled with the fill. After the exchange fills the order, IRL compares what was authorized with what executed and records
MATCHEDorDIVERGENT.
When something goes wrong, you can prove what the agent was allowed to do, what it said it was doing, and what actually happened.
Tools
Behaviour the agent can rely on:
- Fail closed. If IRL is unreachable or denies the intent, no order is sent.
- Kill switch. Create the file
~/.irl-gateway/KILLand every trade is refused before IRL is even called. Delete it to resume. - No silent fills. If the exchange fills but the IRL bind fails, the result still reports the fill and flags it for reconciliation.
- Sealed = sent. Order sizes are rounded to the venue's step and checked against its minimums before IRL seals them, so the sealed quantity is exactly what reaches the exchange. An order the venue would reject is blocked with a plain reason instead.
Quick start (paper trading, about a minute)
That one command gets a free paper-tier token from norve.dev, registers your agent with a starter mandate (BTC/USDT and ETH/USDT, at most 1,000 USDT per order, on paper-binance), saves the credentials to ~/.irl-gateway/agent.json, and prints:
- a
claude mcp add irl-gateway ...line for Claude Code, and - an
mcpServersblock for Claude Desktop, Cursor or any MCP client.
Paste one of them, then ask the agent to call get_policy and make its first paper trade. Paper fills are simulated at live public Binance prices with Binance's real order-size rules, so no exchange keys are needed.
Options: --name, --assets BTC/USDT,SOL/USDT, --max-notional 250, --contact [email protected] (so we can reach you), --server (your own IRL engine).
Free tier limits: paper venues only, up to 3 agents and 500 authorizations a day per token. Want to trade live, or run without limits? Self-host the engine or ask for a full token.
Doing it by hand instead
Then add the gateway to your MCP client:
Configuration
The venue IRL sees is the exchange id (binance), or paper-<exchange> for paper trading, so a mandate can allow paper trading while denying the real account.
How the rationale is sealed
For each trade the gateway builds a context of the rationale, symbol, side, quantity, reference price, venue, model id and client order id. It hashes that context as canonical JSON (sorted keys, no whitespace) with SHA-256 and sends the hash to IRL as prompt_version = "ctx-sha256:<hex>", which IRL seals into the trace's reasoning_hash.
The journal stores the full context next to its hash, so anyone holding a journal line can recompute the hash and match it to the sealed trace. IRL itself never sees the rationale's text.
Development
Status
Early (0.1). Spot market orders only. Paper trading and ccxt exchanges are supported; Alpaca is next. Not investment advice, and no strategy is included: the gateway controls and records what your agent does, it does not decide.
MIT licensed.
Source: README.md at commit 2e6fd99
Tools
0Version history
1- v0.3.0LatestOct 7, 2026


