| name | delphi |
| description | Gensyn Delphi information market tools, including the Delphi agent trading competition. List and filter markets (including verifiable-only filter), fetch market details with live on-chain prices and implied probabilities, quote buy/sell trades, execute buy and sell transactions (with automatic token approval and slippage protection), view portfolio positions, browse trade history, query on-chain event data via Goldsky subgraph (buys, sells, redemptions, liquidations, settlements), check subgraph indexing status, redeem winnings from settled markets, liquidate expired or failed markets, manage ERC-20 token allowances, and check wallet ETH and token balances. Uses the @gensyn-ai/gensyn-delphi-sdk npm package on Gensyn testnet, mainnet, or the agent trading competition (competition-testnet — LMSR markets with their own contracts, token and leaderboard at agent-competition.gensyn.ai). Invoke when the user wants to interact with Delphi information markets or the agent trading competition — browsing, researching, trading, competing, registering for the competition, querying historical on-chain data, managing positions, or checking balances. |
| compatibility | Requires dependencies installed via `npm install`. Only DELPHI_API_ACCESS_KEY and wallet signing credentials are mandatory. Network defaults (RPC URL, chain ID, gateway contract, API URL) are set automatically based on DELPHI_NETWORK (default: testnet). |
Delphi
Gensyn Delphi is a set of tools for deploying and interacting with information markets on Gensyn. Markets are user-owned and permissionless — Gensyn does not control markets, custody funds, or settle trades. The API is maintained for convenience. All interactions go through DelphiClient from the @gensyn-ai/gensyn-delphi-sdk package.
Trading the agent competition? The competition is a separate network
(competition-testnet) using LMSR markets, not the parimutuel markets
described below. The pricing maths, the token, the registration step and the
leaderboard are all different — read
reference/competition.md before trading, and
do not apply the parimutuel section below to it.
How dynamic parimutuel markets work
This section describes Delphi testnet/mainnet. The competition uses LMSR,
where prices sum to 1, spot price is the implied probability, and a winning
share always pays exactly 1 token. See
reference/competition.md.
Dynamic parimutuel markets are betting or information systems where prices (odds) emerge endogenously from the distribution of all participants' wagers rather than being set by a market maker. As new bets flow in, the implied probabilities continuously update: outcomes attracting more capital see their odds shorten (higher implied probability), while less-backed outcomes become cheaper. Liquidity is pooled across all participants, so traders are effectively betting against the aggregate market rather than a counterparty, and the depth of the pool determines how sensitive prices are to new information. This creates a self-adjusting mechanism where prices reflect both current beliefs and the marginal impact of incoming liquidity, often leading to smoother, more stable updates than thin order-book markets while still converging toward consensus probabilities over time.
Important: spot price and expected payout move independently, and payouts are not fixed. Unlike fixed-payout markets (e.g. Polymarket) where a winning share always redeems for exactly $1, Delphi DPM payouts are determined at settlement: the entire pool is divided among winning shareholders, so payout per winning share=total winning shares/total pool.
The spot price is the marginal cost to buy the next share at the current moment — i.e. the local slope of the pricing curve. A probability-like quantity can be inferred from the current pool state and expected redemption value, but it is not identical to the spot price, and the two can diverge substantially depending on liquidity distribution and market depth.
When to use this skill
- User wants to list, search, or browse information markets
- User wants prices, probabilities, or details for a specific market
- User wants to buy or sell outcome shares
- User wants to check their portfolio, positions, or trade history
- User wants to redeem winnings from a resolved market
- User wants to liquidate positions in an expired (unresolved) market
- If the user asks you to create a market, remind them that markets not created on the UI will not show up on the UI
- User wants to check or set token approval for trading
- User wants to query historical on-chain trade data (buys, sells, redemptions, liquidations)
- User wants recent trades for a market or wallet via the Goldsky subgraph
- User wants to check their wallet ETH or token balances
- User wants to get ETH or USDC to fund their wallet for trading (testnet faucet, bridging)
- User wants to trade in, register for, or check their standing in the agent trading competition → load reference/competition.md
- User mentions the competition, the leaderboard,
agent-competition.gensyn.ai, or sets DELPHI_NETWORK=competition-testnet
- Any question about Delphi information markets, or on-chain trading on Gensyn
Installation
npm install
This will install all required dependencies including the SDK, dotenv, viem, and development tools.
Example scripts
This repository includes working example scripts in the scripts/ folder that demonstrate all common operations. These provide a paved path for agents to reference or run directly:
| Script | Purpose | Usage |
|---|
scripts/list-markets.ts | List and filter markets | npx tsx scripts/list-markets.ts [status] [category] [limit] |
scripts/get-market.ts | Get details for a specific market | npx tsx scripts/get-market.ts <market-id> |
scripts/quote-buy.ts | Get buy quote (read-only) | npx tsx scripts/quote-buy.ts <market-address> <outcome-idx> <shares> |
scripts/quote-sell.ts | Get sell quote (read-only) | npx tsx scripts/quote-sell.ts <market-address> <outcome-idx> <shares> |
scripts/quote-redeem.ts | Quote redemption payout for a settled market (read-only) | npx tsx scripts/quote-redeem.ts <market-address> [wallet-address] |
scripts/quote-liquidate.ts | Quote liquidation proceeds for an expired market (read-only) | npx tsx scripts/quote-liquidate.ts <market-address> <outcome-idx>[,<idx>...] [wallet-address] |
scripts/buy-shares.ts | Buy shares (on-chain) | npx tsx scripts/buy-shares.ts <market-address> <outcome-idx> <shares> [slippage-pct] |
scripts/sell-shares.ts | Sell shares (on-chain) | npx tsx scripts/sell-shares.ts <market-address> <outcome-idx> <shares> [slippage-pct] |
scripts/list-positions.ts | List wallet positions | npx tsx scripts/list-positions.ts [wallet-address] |
scripts/redeem.ts | Redeem winnings from settled markets | npx tsx scripts/redeem.ts <market-address> [market-address ...] |
scripts/liquidate.ts | Liquidate positions in expired markets | npx tsx scripts/liquidate.ts <market-address> [market-address ...] |
scripts/token-approval.ts | Check or set token approval | npx tsx scripts/token-approval.ts <market-address> [amount|unlimited] |
scripts/list-recent-trades.ts | List recent trades via subgraph | npx tsx scripts/list-recent-trades.ts <market-proxy-address> [limit] |
scripts/agent-tui/ | Live read-only Ink dashboard (Overview — with Edge View + Agent Logs — · Portfolio · My Activity · Markets, with market drill-down) | npx tsx scripts/agent-tui/index.tsx <wallet-address> <testnet|mainnet|competition-testnet> (both required) · keys: 1-4 screens, ↑↓ select, ⏎ detail, r refresh, q quit (add --once for a single frame) |
scripts/log-event.ts | Append a traceable event to the agent event log (Agent TUI → Overview → Agent Logs) | npx tsx scripts/log-event.ts <type> "<message>" |
scripts/compute-edge.ts | Compute edge (your prob − market's implied prob) for one or more market outcomes; prints the signal and feeds the Agent TUI → Overview → Edge View | npx tsx scripts/compute-edge.ts <market-address> <outcome-idx> <your-prob> [<market> <outcome> <prob> ...] |
scripts/get-wallet-balances.ts | Check ETH and collateral token balances | npx tsx scripts/get-wallet-balances.ts |
scripts/testnet-faucet.ts | Claim 1,000 testnet USDC from the Gensyn faucet | npx tsx scripts/testnet-faucet.ts |
scripts/bridge-eth-to-gensyn-testnet.ts | Bridge ETH from Sepolia to Gensyn Testnet | npx tsx scripts/bridge-eth-to-gensyn-testnet.ts <amount-eth> |
scripts/bridge-eth-to-gensyn-mainnet.ts | Bridge ETH from Ethereum mainnet to Gensyn Mainnet | npx tsx scripts/bridge-eth-to-gensyn-mainnet.ts <amount-eth> |
scripts/bridge-usdc-to-gensyn-mainnet.ts | Bridge USDC from Ethereum mainnet to Gensyn Mainnet via LayerZero | npx tsx scripts/bridge-usdc-to-gensyn-mainnet.ts <amount-usdc> [slippage-pct] |
All scripts use the shared client setup from scripts/client.ts which handles environment variable configuration automatically. You can also run them via npm scripts: npm run list-markets, npm run buy-shares, etc.
Before running scripts
Before running any script in scripts/, ensure the runtime is prepared.
Required setup checklist:
- Install dependencies by running
npm install.
- Verify required environment variables are set:
- Check for a
.env file in the project root (preferred), or
- Verify environment variables are exported in the shell session
- If either check fails, fix it before running any task script.
- Do not call
scripts/*.ts until setup succeeds.
- Do not pass environment variables inline with commands - use
.env file or export statements instead.
Environment variables
Only two things are mandatory: your API key and wallet signing credentials. Everything else has sensible defaults. The SDK defaults to testnet if DELPHI_NETWORK is not set.
Agent instructions for missing env vars:
When required environment variables are not set, do NOT ask the user for their values in chat. Instead:
- Tell the user which variables are needed (list them below).
- Tell them where to get each value.
- Ask them to create a
.env file in the project root themselves with those values.
- Wait for them to confirm the file is created before proceeding.
- NEVER read the
.env file — treat it as a secret store the agent must not access.
Mandatory variables to communicate to the user:
Plus one of these signing options (tell the user to pick one):
Option A — Private key
| Variable | Description |
|---|
DELPHI_SIGNER_TYPE | Set to private_key |
WALLET_PRIVATE_KEY | 0x-prefixed hex private key for their wallet |
Option B — Coinbase CDP Server Wallet (default signer, no DELPHI_SIGNER_TYPE needed)
Make sure to also convey the following 2 points to the user -
-
For the CDP option, private keys are secured in Coinbase's Trusted Execution Environment (TEE) and never leave the TEE. See Server Wallet v2 docs for details.
-
To execute Delphi transactions, your signer wallet must have ETH (for gas) and USDC on the Gensyn chain.
Network selection
| Variable | Values | Default |
|---|
DELPHI_NETWORK | "testnet" | "mainnet" | "competition-testnet" | "testnet" |
The SDK defaults to testnet — DELPHI_NETWORK is optional. Only set it if the user explicitly wants mainnet or the competition.
When DELPHI_NETWORK=testnet (default), the SDK automatically uses:
- RPC URL:
https://gensyn-testnet.g.alchemy.com/public
- Chain ID:
685685
- Gateway:
0x22ea355D7218Dc86b4c83732cBbd01f7Ff2332b3 (automated settlement)
- Factory:
0x97d2b3F0614C8189343A38094629FCE2910b727A
- Legacy gateway:
0x7b8FDBD187B0Be5e30e48B1995df574A62667147 (pre-automated-settlement markets)
- Token:
0x0724D6079b986F8e44bDafB8a09B60C0bd6A45a1
- API URL:
https://delphi-api.gensyn.ai/
- Subgraph URL:
https://api.goldsky.com/api/public/project_cmnoqdag1obop01z3efnu8ssq/subgraphs/delphi-testnet-autoset/1.0.0/gn
When DELPHI_NETWORK=mainnet, the SDK automatically uses:
- RPC URL:
https://gensyn-mainnet.g.alchemy.com/public
- Chain ID:
685689
- Gateway:
0x982a67aE92D8de361957249fB2BB4a62BCc6A8d5 (automated settlement)
- Factory:
0x9C73417f79a1361c6aF9Bd828343badEE1b84936
- Legacy gateway:
0x4e4e85c52E0F414cc67eE88d0C649Ec81698d700 (pre-automated-settlement markets)
- Token:
0x5b32c997211621d55a89Cc5abAF1cC21F3A6ddF5
- API URL:
https://api.delphi.fyi/
- Subgraph URL:
https://api.goldsky.com/api/public/project_cmnoqdag1obop01z3efnu8ssq/subgraphs/delphi-mainnet-autoset/1.0.0/gn
When DELPHI_NETWORK=competition-testnet (the agent trading competition), the SDK automatically uses:
- RPC URL:
https://gensyn-testnet.g.alchemy.com/public (same chain as testnet)
- Chain ID:
685685
- Gateway:
0x097599c9D966fF496284b892A8F13BF885b258ef (LmsrGateway — single deployment, no legacy)
- Factory:
0xEa9D0a78d0209916e88e363B8FDa3e23206Ff49b
- Token:
0x8A2d75753362Eb5D5669a2c22cbf394b26a0571F (TST, 6 decimals — not USDC)
- API URL:
https://delphi-api.gensyn.ai/ (shared testnet deployment; the client sends X-Delphi-Mode: competition automatically)
- Subgraph URL:
https://api.goldsky.com/api/public/project_cmnoqdag1obop01z3efnu8ssq/subgraphs/delphi-agent-competition/1.0.0/gn
- Leaderboard:
https://agent-competition.gensyn.ai
The competition is not just different addresses. It uses LMSR pricing
(winning shares pay exactly 1 token, prices sum to 1), needs a testnet
API key, and needs your wallet registered via DoraHacks before you can rank.
Read reference/competition.md before trading it.
Delphi runs two deployments side by side. Every new market is created on the
automated-settlement gateway, which is settled by an oracle; older markets live on the
legacy gateway. Each gateway rejects the other's markets, so the SDK resolves the right
one per market — pass any market address and it works. The subgraph default, however,
covers the automated deployment only: subgraph queries for a legacy market come back
empty (see reference/subgraph.md).
Because settlement is now automated, a market can end up failed — the oracle ran but
could not resolve the question. A failed market has no winning outcome, so
redeemMarket() reverts and funds are recovered with liquidate(), exactly as for
expired. Full status list: open, awaiting_settlement, settled, expired,
failed.
The addresses and subgraph endpoints above, plus client.resolveGateway(),
client.getMarketStatus() and subgraph.getMarketSettlement(), require
@gensyn-ai/gensyn-delphi-sdk@^2.0.0 (pinned in package.json). On an older SDK the
defaults still point at the legacy gateway and those methods do not exist.
Optional overrides
These override the network defaults if you need to point at a custom endpoint:
| Variable | Description |
|---|
GENSYN_RPC_URL | Custom RPC endpoint |
GENSYN_CHAIN_ID | Custom chain ID |
DELPHI_GATEWAY_CONTRACT | Custom gateway address. Pins every call to this gateway and disables per-market routing — calls for markets it does not own will revert |
DELPHI_LEGACY_GATEWAY_CONTRACT | Custom legacy gateway address |
DELPHI_FACTORY_CONTRACT | Custom automated-settlement factory (used to route markets) |
DELPHI_LEGACY_FACTORY_CONTRACT | Custom legacy factory (used to route markets) |
DELPHI_API_BASE_URL | Custom API base URL |
DELPHI_SUBGRAPH_URL | Custom Goldsky subgraph endpoint |
DELPHI_TOKEN_ADDRESS | Override the ERC-20 collateral token address |
DELPHI_SIGNER_TYPE | "private_key" or "cdp_server_wallet" (default) |
DELPHI_COMPETITION_ID | Competition UUID scoping market reads in list-markets.ts, get-market.ts and the Agent TUI (competition networks only; ignored otherwise). Unset = the active competition |
Client setup
import {
DelphiClient,
SubgraphClient,
createPrivateKeySigner,
createCdpSigner,
} from "@gensyn-ai/gensyn-delphi-sdk";
const client = new DelphiClient();
Units
| Type | Raw representation | Human conversion |
|---|
| Shares | 18-decimal bigint | 1n * 10n**18n = 1 share |
| USDC | 6-decimal bigint | 1_000_000n = 1 USDC |
| Implied probability (on-chain bigint) | 18-decimal (1e18 = 100%) | 5n * 10n**17n = 50% |
| Spot price (on-chain bigint) | 6-decimal (1e6 = 1.0 USDC/share) | 600_000n = 0.60 USDC/share |
market.spotPrices[i] | plain number float | 0.6 = 0.60 USDC/share — already human-readable |
market.spotImpliedProbabilities[i] | plain number float (0–1) | 0.6 = 60% — already human-readable |
const sharesToBigint = (n: number) => BigInt(Math.round(n * 1e18));
const usdcToBigint = (n: number) => BigInt(Math.round(n * 1e6));
const toUsdc = (n: bigint) => `${(Number(n) / 1e6).toFixed(6)} USDC`;
const toShares = (n: bigint) => `${(Number(n) / 1e18).toFixed(4)} shares`;
const toProb = (n: bigint) => `${(Number(n) / 1e18 * 100).toFixed(2)}%`;
const toSpotPrice = (n: bigint) => `${(Number(n) / 1e6).toFixed(4)} USDC/share`;
Core patterns
Tip: See scripts/list-markets.ts for a complete working example.
List markets
const { markets } = await client.listMarkets({
status: "open",
category: "crypto",
limit: 20,
skip: 0,
orderBy: "liquidity",
verifiable: true,
pricesAndImpliedProbabilities: true,
});
for (const market of markets ?? []) {
const meta = market.metadata;
console.log(market.id, meta?.question);
}
Get a single market
Tip: See scripts/get-market.ts for a complete working example.
const market = await client.getMarket({ id: "<market-id>", pricesAndImpliedProbabilities: true });
const meta = market.metadata;
Live prices
The simplest way to get live prices is pricesAndImpliedProbabilities: true in listMarkets or getMarket — the SDK fetches them via multicall and returns human-readable floats on the market object:
if (market.spotPrices && market.spotImpliedProbabilities) {
for (let i = 0; i < (meta?.outcomes?.length ?? 0); i++) {
console.log(`[${i}] price: ${market.spotPrices[i].toFixed(4)} USDC/share | prob: ${(market.spotImpliedProbabilities[i] * 100).toFixed(2)}%`);
}
}
For custom on-chain reads (advanced), use the Gateway ABI directly via viem — see reference/onchain.md.
Quote buy (read-only, no gas)
Tip: See scripts/quote-buy.ts for a complete working example.
const { tokensIn } = await client.quoteBuy({
marketAddress: "0x..." as `0x${string}`,
outcomeIdx: 0,
sharesOut: BigInt(Math.round(10 * 1e18)),
});
const costUsdc = Number(tokensIn) / 1e6;
Quote sell (read-only, no gas)
Tip: See scripts/quote-sell.ts for a complete working example.
const { tokensOut } = await client.quoteSell({
marketAddress: "0x..." as `0x${string}`,
outcomeIdx: 0,
sharesIn: BigInt(Math.round(5 * 1e18)),
});
const payoutUsdc = Number(tokensOut) / 1e6;
Quote redeem / liquidate (read-only, no gas)
For closed markets, spot price no longer reflects what a position is worth — the realizable value is the redemption payout (settled) or liquidation proceeds (expired). These quotes simulate the on-chain redeem/liquidate via eth_call (no gas, no state change) and throw if the position isn't redeemable/liquidatable (e.g. a losing settled outcome, or a market not yet closed), so wrap them in try/catch.
Tip: See scripts/quote-redeem.ts and scripts/quote-liquidate.ts for complete working examples.
const { sharesIn, tokensOut } = await client.quoteRedeem({
marketAddress: "0x..." as `0x${string}`,
account: "0x..." as `0x${string}`,
});
const payoutUsdc = Number(tokensOut) / 1e6;
const { sharesIn: burned, totalTokensOut } = await client.quoteLiquidate({
marketAddress: "0x..." as `0x${string}`,
outcomeIndices: [0, 1],
account: "0x..." as `0x${string}`,
});
const proceedsUsdc = Number(totalTokensOut) / 1e6;
Valuing a portfolio across statuses: use spot (shares × spotPrice) only for open markets. For settled markets value the winning outcome via quoteRedeem (losing outcomes are worth 0) and for expired markets via quoteLiquidate. The Agent TUI's Portfolio tab does exactly this and shows a per-position status badge.
Buy shares (on-chain, with auto-approval)
Tip: See scripts/buy-shares.ts for a complete working example.
const marketAddress = "0x..." as `0x${string}`;
const outcomeIdx = 0;
const sharesOut = BigInt(Math.round(10 * 1e18));
const { tokensIn } = await client.quoteBuy({ marketAddress, outcomeIdx, sharesOut });
const maxTokensIn = tokensIn * 102n / 100n;
await client.ensureTokenApproval({ marketAddress, minimumAmount: maxTokensIn });
const { transactionHash } = await client.buyShares({
marketAddress,
outcomeIdx,
sharesOut,
maxTokensIn,
});
Sell shares (on-chain)
Tip: See scripts/sell-shares.ts for a complete working example.
const sharesIn = BigInt(Math.round(5 * 1e18));
const { tokensOut } = await client.quoteSell({ marketAddress, outcomeIdx, sharesIn });
const minTokensOut = tokensOut * 98n / 100n;
const { transactionHash } = await client.sellShares({
marketAddress,
outcomeIdx,
sharesIn,
minTokensOut,
});
List positions
Tip: See scripts/list-positions.ts for a complete working example.
Important: Positions with shares equal to 0 (i.e. BigInt(p.shares) === 0n) represent fully exited stakes. These cannot be redeemed or liquidated since the wallet holds no shares. Always filter out zero-share positions before attempting redeem or liquidate operations.
const { positions } = await client.listPositions({
wallet: "0x...",
redeemedOrLiquidated: false,
limit: 50,
});
for (const p of positions ?? []) {
const shares = Number(BigInt(p.shares)) / 1e18;
if (shares === 0) continue;
console.log(`Market ${p.marketProxy} | Outcome ${p.outcomeIdx} | ${shares} shares`);
}
Redeem settled positions
Tip: See scripts/redeem.ts for a complete working example.
Important: Only positions with non-zero shares can be redeemed. If listPositions returns a position with shares === "0", the wallet has no stake in that market and calling redeemMarket will fail or return nothing. Always check shares > 0 before redeeming.
const { transactionHash, sharesIn, tokensOut } = await client.redeemMarket({
marketAddress: "0x..." as `0x${string}`,
});
const { results, totalTokensOut } = await client.redeemPositions({
marketAddresses: ["0x...", "0x..."],
});
for (const r of results) {
if (r.success) console.log(`Redeemed ${Number(r.tokensOut!) / 1e6} USDC from ${r.marketAddress}`);
else console.error(`Failed ${r.marketAddress}: ${r.error}`);
}
Liquidate expired positions
Tip: See scripts/liquidate.ts for a complete working example.
Liquidation is for positions in expired markets that were never settled. Unlike redemption (which is for settled markets with a winner), liquidation recovers tokens from markets that expired without resolution.
const { transactionHash, sharesIn, totalTokensOut } = await client.liquidate({
marketAddress: "0x..." as `0x${string}`,
outcomeIndices: [0, 1],
});
const { positions } = await client.listPositions({ wallet, redeemedOrLiquidated: false });
const outcomeIndices = positions!
.filter(p => p.marketProxy === marketAddress && BigInt(p.shares) > 0n)
.map(p => Number(p.outcomeIdx));
Token approval
Tip: See scripts/token-approval.ts for a complete working example.
const { ownerAddress, allowance } = await client.getTokenAllowance({ marketAddress });
await client.approveToken({ marketAddress });
await client.approveToken({ marketAddress, amount: 50_000_000n });
const { approvalNeeded, allowance, transactionHash } = await client.ensureTokenApproval({
marketAddress,
minimumAmount: requiredTokens,
approveAmount: 100_000_000n,
});
Check wallet balances
Tip: See scripts/get-wallet-balances.ts for a complete working example.
const ethBalance = await client.getEthBalance();
console.log(`ETH: ${(Number(ethBalance) / 1e18).toFixed(6)}`);
const tokenAddress = client.getTokenAddress();
const { balance, decimals } = await client.getErc20BalanceWithDecimals();
const formatted = (Number(balance) / 10 ** decimals).toFixed(decimals > 6 ? 6 : decimals);
console.log(`Token (${tokenAddress}): ${formatted}`);
const raw = await client.getErc20Balance();
Query recent trades via subgraph
Tip: See scripts/list-recent-trades.ts for a complete working example.
The SDK's SubgraphClient queries on-chain event data indexed by a Goldsky subgraph. Access it via client.getSubgraph().
const subgraph = client.getSubgraph();
const { buys, sells } = await subgraph.getMarketTrades(
"0x..." as string,
{ first: 20 }
);
for (const buy of buys) {
const cost = Number(BigInt(buy.tokensIn ?? "0")) / 1e6;
const shares = Number(BigInt(buy.sharesOut ?? "0")) / 1e18;
const time = new Date(Number(buy.timestamp_) * 1000).toLocaleString();
console.log(`BUY ${time} | ${cost.toFixed(4)} USDC → ${shares.toFixed(4)} shares`);
}
const data = await subgraph.query<{ gatewayBuys: SubgraphBuy[] }>(`{
gatewayBuys(first: 5, orderBy: timestamp_, orderDirection: desc) {
id buyer marketProxy tokensIn sharesOut timestamp_
}
}`);
const meta = await subgraph.getMeta();
console.log(`Block: ${meta.block.number}, indexing errors: ${meta.hasIndexingErrors}`);
Available entities: gatewayBuys, gatewaySells, gatewayRedemptions, gatewayLiquidations, gatewayMarketSettleds, gatewayMarketFaileds, marketResolutionRequesteds. All support filtering (where), ordering (orderBy + orderDirection), and pagination (first + skip). Note gatewayWinnerSubmitteds does not exist on the automated-settlement subgraph — querying it is a hard GraphQL error; use gatewayMarketSettleds, which has the same payload.
TUI
The user can visualize what the agent is doing live with the read-only Agent TUI dashboard — portfolio, positions, activity, markets, an Edge View and an Agent Logs reasoning stream — via npx tsx scripts/agent-tui/index.tsx <wallet-address> <testnet|mainnet|competition-testnet> (or npm run agent-tui -- <wallet-address> <testnet|mainnet|competition-testnet>). The two helpers below feed its Agent Logs and Edge View panels.
Tracing your reasoning (Agent Logs)
log-event populates the Agent TUI's Agent Logs panel. Use it at genuine decision points: log why you're acting (THINK), then log the action you took. Event types:
| Type | Use for |
|---|
THINK | The reasoning — what you observed, why the market looks mispriced, what edge you see, why this side and size. The important one. |
BUY | A buy you executed. |
SELL | A sell you executed. |
LIQUIDATE | Liquidating positions in an expired market. |
REDEEM | Redeeming winnings from a settled market. |
SKIP | A market you looked at and deliberately passed on (and why). |
npx tsx scripts/log-event.ts THINK "<the reasoning — why this trade>"
npx tsx scripts/log-event.ts BUY "<the action you took>"
THINK is the important one — capture the reasoning. This is what the Agent Logs panel exists to show.
- The action types (
BUY/SELL/LIQUIDATE/REDEEM) are short notes of what followed the think. Keep them brief — the My Activity tab already shows the trade mechanics (amounts, prices, tx hashes), so don't restate them.
- Use
SKIP to record markets you evaluated but passed on, so the log shows what you considered, not just what you traded.
Do not just describe the order. "Buy 10 YES on Wild Pandas, 2% slippage" is exactly what Activity already shows — log the why instead.
Good:
npx tsx scripts/log-event.ts THINK "BTC $99,999 by Jun 31: ~12 days left and price is still ~\$25k away — that move is unlikely, yet the market prices NO at only 71%. Taking NO; small testnet size to validate."
npx tsx scripts/log-event.ts BUY "10 NO on BTC $99,999"
Log a THINK→action pair at genuine decision points, not every routine read. The <type> is case-insensitive and normalised to upper case. Events append to $DELPHI_AGENT_LOG (default ~/.delphi/agent-events.jsonl); the file is created automatically.
Computing edge before trading (Edge View)
Edge is the core trade signal — always compute it before you autonomously decide to buy or sell a market. Edge is the gap between your own probability estimate for an outcome and the market's live implied probability:
edge = your probability − market's implied probability
A positive edge means the outcome is underpriced relative to your view (a buy candidate); a negative edge means it's overpriced (a sell / avoid). The bigger the absolute gap, the stronger the signal.
scripts/compute-edge.ts fetches the market's live implied probability, computes the edge against your estimate, prints the signal, and persists it so it shows up — ranked by gap size — in the Agent TUI's Edge View (Overview screen).
npx tsx scripts/compute-edge.ts 0x1234…abcd 1 0.30
npx tsx scripts/compute-edge.ts 0x1234…abcd 1 0.30 0x5678…ef01 0 0.62
<your-prob> is your estimate for that outcome (0–1 like 0.30, or a percent like 30); <market-address> is the market id from listMarkets/getMarket, and <outcome-idx> is the outcome's index. Re-running for the same (market, outcome) supersedes the previous value (latest wins).
Required decision flow when deciding whether to buy/sell a market autonomously:
- Form your own probability estimate for the outcome.
- Run
compute-edge.ts to compare it against the market's live implied probability.
- Use the resulting edge to drive the decision — only trade where the edge is meaningfully positive (buy) or negative (sell), and prefer larger gaps. If the edge is small or the wrong sign,
SKIP.
- Then
log-event THINK your reasoning (referencing the edge) and log-event BUY/SELL the action you took.
Edges persist to $DELPHI_AGENT_EDGES (default ~/.delphi/agent-edges.jsonl); the file is created automatically. The Edge View re-joins your stored probability against the live market price on every refresh, so the displayed edge stays current as the market moves.
Error handling
| Error | Cause | Fix |
|---|
TokensInExceedsMax | Price moved above maxTokensIn | Re-quote, increase slippage |
TokensOutBelowMin | Price moved below minTokensOut | Re-quote, increase slippage |
MarketNotOpen | Market is closed or settled | Check market.status first |
SharesInExceedSupply | Selling more shares than held | Check position before selling |
Requires apiKey | Missing DELPHI_API_ACCESS_KEY | Set env var |
Requires rpcUrl | Missing GENSYN_RPC_URL | Set env var or let network default apply |
Requires privateKey | Missing WALLET_PRIVATE_KEY | Set env var or switch to CDP signer |
CDP signing requires ... | Missing CDP env vars | Set all CDP_ vars |
Reference files (load on demand)
| File | When to load |
|---|
| reference/markets.md | Full listMarkets/getMarket params, Market type schema, metadata structure |
| reference/trading.md | Trading mechanics, slippage formulas, parimutuel pricing explainer |
| reference/positions.md | Position/Trade type schemas, batch redemption patterns, portfolio estimation |
| reference/onchain.md | Full Gateway ABI function list, direct viem read patterns, signing config |
| reference/subgraph.md | Goldsky subgraph GraphQL schema, SubgraphClient API, entity types, filtering, raw query examples |
| reference/funding.md | Getting ETH and USDC onto Gensyn (testnet faucet, OP Stack bridge, LayerZero USDC bridge) |
| reference/competition.md | The agent trading competition: LMSR vs parimutuel pricing, registration, trading differences, the leaderboard, subgraph differences, failure modes |