← Plugin catalog
Finance

Co-Invest

Liquid v1.1.0

Research global markets 24/7

Create a free account to save this plugin.

From the developer

Not specified in the available declarations: capabilities, limitations, pricing & account requirements.

Onboarding example

What moved NVDA in the last 24 hours?
Sources & dates

Developer declarations; not independently tested. Listing last checked Nov 22, 2026. Package observed Nov 22, 2026.

View package source →

Description

From the marketplace listing

Co-Invest brings Liquid market research and portfolio planning into ChatGPT. Ask about crypto, equities, commodities, indices and prediction markets and get live prices, funding, positioning, technical indicators, charts and news. Review your Liquid portfolio, open orders and history, and model an allocation that fits your risk and time horizon. When you want to act, Co-Invest prepares the trade and opens Liquid, our brokerage, with the idea ready for your final review; live orders are not placed from ChatGPT. A paper account with simulated funds lets you practice and manage simulated positions. Designed for traders who want sharper context, faster planning, and a more connected way to navigate Liquid markets.

Language: English · Automatically detected from descriptions.

What changed

· 3 observations

Capabilities & instructions

Full description changed from “market research and portfolio planning into ChatGPT. Explore Liquid market data, news catalysts, positioning trends, portfolio context, and trading tools in...” to “Liquid market research and portfolio planning into ChatGPT. Ask about crypto, equities, commodities, indices and...

View comparison →

Technical updates · 1

Package or technical metadata updated

View technical comparison →

· 3 observations

Capabilities & instructions

App-6a20e26c6ab8819191519e2811e03522 updated; open the comparison for details. Co-invest updated; open the comparison for details. Logo url dark changed from “https://files.openai.com/content?id=file_00000000f9f871fd8406e8d1e83bbe5d” to “https://files.openai.com/content?id=file_00000000b72881f4a8002065fd101dd7”....

View comparison →
Capabilities & instructions

App-6a20e26c6ab8819191519e2811e03522 updated; open the comparison for details. Co-invest updated; open the comparison for details. Logo url dark changed from “https://files.openai.com/content?id=file_00000000f9f871fd8406e8d1e83bbe5d” to “https://files.openai.com/content?id=file_00000000b72881f4a8002065fd101dd7”....

View comparison →

Technical updates · 1

Package or technical metadata updated

View technical comparison →

Similar plugins

Finding similar plugins… Results will appear here automatically.

Browse plugins →

Files & skills

File archives

Plugin package12 files · 26.2 KBBrowse files →
Skill instructions
coinvest-allocate4.74 KB

View saved version →

---
name: coinvest-allocate
description: "Build a multi-position allocation on Liquid with plan_portfolio: collect risk tolerance, time horizon and asset classes, then present one sized basket and place it or hand over a review link as this connection allows. Triggers on: build me a portfolio, plan a portfolio, how should I deploy my balance, allocate my balance, balanced book across stocks gold and crypto. Places nothing without an explicit request."
license: MIT
---

# Co-Invest allocation

Turn an allocation request into one proposed basket from `plan_portfolio`, then stop for the user's decision. A single trade is not an allocation; use the trade workflow for that.

## Workflow

1. Read `paper_trading_status` so the plan is labeled live or paper, and `get_portfolio` for the balance and existing positions.
2. Collect three answers the way the `plan_portfolio` description requires: where it requires the host's native question UI, use it and never a numbered list in chat; where it allows chat, ask in chat:
   - risk tolerance: `conservative`, `moderate` or `aggressive`;
   - time horizon: `intraday`, `swing_week` or `position_long_term`;
   - asset classes, one or more of `crypto`, `equities`, `commodities`, `indices`, `fx`.

   Do not ask about the balance.
3. Call `plan_portfolio` once with those answers, plus any leverage cap, themes and a one-line `user_intent` the user gave.
4. Write a short thesis, then prepare the basket. If the description of `plan_portfolio` names `suggest_trades_batch`, call it once with the thesis and every leg. Present each leg's asset, side, notional and leverage, and a short risk summary. Keep current holdings apart from proposed legs.
5. End by asking whether to place the basket. Branch on the live tool list:
   - `execute_orders_batch` is described as internal or called by a confirmation control: never call it. The basket is placed only when the user confirms the returned `suggest_trades_batch` proposal with its own confirmation control; a typed "yes" in chat does not place it and the agent must not call the executor after one. If the host shows no confirmation control, say this connection cannot place it from chat.
   - `execute_orders_batch` takes `confirmed`: place it only after the user approves the exact returned legs and execution mode, with `confirmed=true`.
   - `execute_orders_batch` has no `confirmed`: it runs when called, so call it once only after an explicit yes to placing this basket.
   - No executor: the review link from `suggest_trades_batch` is the result. The user finishes in Liquid.

## Tools

- `plan_portfolio`: research bundle and sizing rules from the three answers. It has no amount input and assumes the whole available balance. Say so when presenting the plan.
- `suggest_trades_batch`: one basket proposal of 2 to 8 legs (the schema limit). Scaling a leg changes the terms and needs a new proposal.
- `execute_orders_batch`: place the reviewed basket. Where it takes `confirmed`, copy the returned legs, `executionMode` and thesis unchanged, generate one stable `idempotencyKey` for this basket and reuse it for reconciliation, and add no proposal-only fields such as `requestedLeverage`.
- `get_portfolio`: balance, mode and current positions before and after.
- `paper_trading_status`: live or paper, read before the plan and before placing.

## Rules

- A plan is a proposal, not an order. Never describe it as executed.
- A tool whose description marks it internal or do-not-call is called only as that description allows; the basket then needs the user's confirmation through the returned proposal's own control, never a typed "yes" followed by an executor call.
- Where `execute_orders_batch` takes `confirmed`, `confirmed=true` follows the user's approval of the exact basket in chat. A changed leg, size or leverage needs a new proposal and a new approval.
- Place a basket with one `execute_orders_batch` call, never one order per leg.
- A saved automation policy never supplies `conf

Preview of the first 4,000 characters. Read full instructions →

coinvest-earn-vaults806 Bytes

View saved version →

---
name: coinvest-earn-vaults
description: Compare Earn or vault options using read-only data exposed by the connected Co-Invest service, when available.
---

# Co-Invest Earn and vault research

Use only read-only Earn or vault tools exposed by the connected Co-Invest service. Do not assume these tools exist: if none are available, explain that the requested data cannot be retrieved through this connection. Do not switch endpoints or call raw APIs to bypass that limitation.

Compare only terms returned by the tools, such as yield basis and period, fees, liquidity, lockups, and stated risks. Distinguish historical or estimated yields from guarantees, and do not extrapolate missing values. This skill is for research only: never initiate deposits, withdrawals, transfers, or other fund movements.
coinvest-funding3.56 KB

View saved version →

---
name: coinvest-funding
description: "Get a Liquid account funded and ready through Co-Invest: the deposit link, a deposit address for a named token and chain, a card or app on-ramp, the trading setup link, the user's payment link and referral link. Triggers on: deposit, fund my account, add money, deposit address, on-ramp, buy with card, enable trading, set up trading, payment link, get paid, referral, refer a friend, invite friends."
license: MIT
---

# Co-Invest funding

Moves a user from no balance to ready to trade, and shares their payment and referral links. None of these tools trades; they return links, addresses or deposit options for the user to act on.

## Workflow

1. To fund the account, call `show_deposit` and show what it returns plainly. It does not move funds.
2. If the user names both a token and a chain, call `generate_deposit_address`. If either is missing, use `show_deposit` instead. Show the returned address, chain and the `direct` flag as given.
3. If the user asks to deposit a specific fiat amount by card or app and `create_onramp_session` is a normal tool on this connection, call it with the amount (2 to 1,000,000) and method, then show the returned URL plainly. Follow that tool's own description on this connection. If it is marked INTERNAL or do not call directly, do not call it; use `show_deposit` and let the user pick in the deposit view.
4. If trading is blocked by setup, or the user asks to enable trading, call `enable_trading` and show the returned link. It does not enable trading by itself; the user finishes setup in Liquid. Where its description says this connection cannot execute live trades, say that setup does not change that.
5. For a payment link call `payment_link`; for a referral link and stats call `refer`. Report what they return.

## Tools

- `show_deposit`: the deposit link or options for funding by card, other apps or wallet transfer.
- `generate_deposit_address`: one address for one token on one chain. Tokens are USDC, USDT, BTC, ETH, SOL on a chain from the schema's `chain` list; where the description lists chains per token, follow it. Other tokens or chains are refused.
- `create_onramp_session`: a hosted on-ramp URL for a fiat amount, where this connection allows calling it directly.
- `enable_trading`: checks account readiness and returns the setup link.
- `get_account`: the public address of the trading account, for identification only.
- `payment_link`: the user's public Liquid profile link where others can send them USDC.
- `refer`: the user's referral link and referral statistics.

## Rules

- Never present the trading account address from `get_account` as a deposit address. It is not a deposit or bridge destination.
- Do not guess a token or chain, and do not call `generate_deposit_address` for a general "how do I deposit" question.
- A deposit into the Earn vault is not funding; the yield skill owns that.
- Before sharing a payment link, say that it opens the user's public profile page, which also shows their trading activity.
- Addresses with `direct` false are bridge addresses. Say so and do not describe them as the user's own wallet.
- These tools take no order approval, but never call one the user did not ask for, and do not retry on an error without a new request.
- Do not state deposit times, fees or limits that the tool results do not return.

## If something is missing

- No Co-Invest connection: say so and point to the host's Co-Invest connector settings.
- A tool is absent from the live tool list: say this connection cannot do it, offer what the remaining tools return, and do not switch endpoints or modes.
coinvest-market-research766 Bytes

View saved version →

---
name: coinvest-market-research
description: Research markets with data from tools exposed by the connected Co-Invest service, when available.
---

# Co-Invest market research

Use the connected Co-Invest tools that are currently available to research the user's requested market, asset, or time period. Select only the exposed tools relevant to the question; do not switch endpoints or call raw APIs to obtain missing capabilities.

Ground prices, news, and technical context in returned results. Include the source and timestamp or period when provided, distinguish reported data from interpretation, and call out stale or incomplete results. If a requested data type is unavailable, say so instead of inventing values or implying that the service supports it.
coinvest-market-scan5.52 KB

View saved version →

---
name: coinvest-market-scan
description: "Scan the whole Liquid market with Co-Invest: what is moving and why, crowded trades, a short list of ideas, the trader leaderboard and your own rank, and changes to your watchlist. Triggers on: what's moving, market overview, market briefing, what's crowded, top setups, any signals, give me ideas, who tops the leaderboard, my leaderboard rank, edit my watchlist."
license: MIT
---

# Co-Invest market scan

Answer market-wide questions with data from the connected Co-Invest server: what is moving, where traders are crowded, which ideas are worth a look, and who leads the leaderboard. It places no trades; acting on an idea is a separate request.

## Workflow

1. Market overview: call `get_news` and `search_markets` (and `show_market_overview` only if the user asks to see all markets), then `get_positioning_pulse`. The no-query `search_markets` result is only the top markets by volume. Where equity themes matter, you may add `upcoming_earnings` (`window` week) to name earnings catalysts. If `search_prediction_markets` returns relevant markets, you may mention two or three with the probability of the specific outcome returned; do not call one leg of a multi-outcome market the leader without the full outcome list. Tie each theme to returned headlines and cite the links. Say what is moving and why, from the returned data only.
2. Signals: `get_news` for the unusual-activity section and `get_positioning_pulse` for crowded long and short buckets. Report a few of the clearest observations with their evidence and a counterpoint. If no setup is verified, say so plainly. Do not claim to monitor markets between turns.
3. Ideas: first run the overview reads (`get_news`, `search_markets` with no query, `get_positioning_pulse`). As the final step you may call `market_picks` with picks grounded in those results, using the count its description asks for (five on some connections unless fewer catalysts qualify). Without it, give a short written list of up to three. For a shortlist you want to compare, use `analyze_markets_batch`. Never invent prices, levels, sizes or leverage.
4. Leaderboard: `leaderboard_data` for the board, `leaderboard_rank` for one trader or the user's own rank. Default to the top three and report only what is returned: ranks, PnL, bias and biggest position, with `duration` as the ranking window, not the time a position was held. A rank-only result has no positions; do not infer them. Leaderboard figures are public Liquid rankings, never the user's paper results. Never suggest copying or mirroring another trader; offer research on the asset instead.
5. Watchlist: `edit_watchlist` only on an explicit request to add, remove, set or clear symbols. No tool reads the watchlist; never call `edit_watchlist` to view it. If the user asks to see it, say this connection can only change it.

## Tools

- `show_market_overview`: the whole multi-asset market; only when the user asks to see all markets. Not for one asset.
- `search_markets`: browse or find tradeable markets; omit the query for the top markets by volume.
- `get_news`: headlines with source links plus an unusual-activity section.
- `get_positioning_pulse`: crowded long-heavy and short-heavy markets; `limit` is rows per bucket, 1 to 20, default 5.
- `market_picks`: 1 to 5 news-driven picks, proposal only. Set `asset` to the exact symbol a tool returned, `displayName` to the user-facing name, `catalyst` to a headline `get_news` returned and `side` to long or short; never show internal ids to the user. Call it ONLY as the final step of the ideas flow in step 3, after `get_news`, `search_markets` and `get_positioning_pulse`. Never for one asset. After it, ask which pick the user wants; do not draft a trade proposal until they choose. A chosen pick becomes a separate trade request that still needs the size (and leverage) from the user before any proposal.
- `analyze_markets_batch`: compare 2 to 10 markets side by side.
- `leaderboard_dat

Preview of the first 4,000 characters. Read full instructions →

coinvest-paper-trading3.5 KB

View saved version →

---
name: coinvest-paper-trading
description: "Practice on Liquid with Co-Invest paper trading: check whether paper mode is on, switch it on or off, and reset the simulated account. Triggers on: paper trade, practice mode, simulate, try without real money, reset my paper account, fresh paper balance, go back to live, am I paper trading."
license: MIT
---

# Co-Invest paper trading

Paper mode makes this connection's account reads and trading actions use Liquid's paper simulator instead of real funds. This skill checks and changes that mode only when the user asks.

## Workflow

1. Read `paper_trading_status` first and report the mode it returns.
2. Change the mode only on an explicit request:
   - "paper trade", "practice", "simulate": `enable_paper_trading`.
   - "go live", "stop paper trading": `disable_paper_trading`. Say first that later orders may use real funds; where its description says this connection places no live orders, say live orders are placed only in Liquid.
   - "reset my paper account", "start over": `reset_paper_account`. Say first what its description lists it clears (positions, orders, fills, and the balance; where stated, funding history, leverage overrides and a reset to 10,000 USD), that it cannot be undone, and follow any separate host approval it asks for. It runs only while paper mode is on.
3. Read `paper_trading_status` again and report the mode it now shows.
4. Label every later number as paper while the mode is on.

## Tools

- `paper_trading_status`: whether paper mode is on for this wallet.
- `enable_paper_trading`: turn paper mode on for this wallet; calling it twice keeps it on. On a permanently paper-only connection it only confirms that and changes no wallet setting.
- `disable_paper_trading`: return to live account data; calling it when paper is off does nothing.
- `reset_paper_account`: restore the simulated account to its starting state; refuses in live mode.

## Rules

- These are direct tools and take no `confirmed` argument: the user's explicit request is the approval, so call each once per request and never as a side effect of another task.
- Where the descriptions say so, the paper account is keyed by wallet on a shared simulator: enabling, disabling or resetting here also applies wherever else this wallet trades paper, including other Liquid MCP connectors. A reset always applies to the wallet's shared paper account and also wipes paper positions and orders open elsewhere.
- Paper mode does not switch the Liquid web app; orders placed there may use real funds. Say so if the user assumes otherwise.
- Some live-only actions, such as spot orders, are refused in paper mode. Report the refusal as given.
- A request for a paper trade while the account is live is not a request to switch modes: ask whether to turn paper mode on, and switch only on a yes. A request to switch to paper mode is the approval.
- Never report a paper balance or PnL as real, and never reuse live figures as paper figures.
- On a connection that is permanently paper-only, `paper_trading_status` says so and there is no way to go live from here; report that instead of trying to switch.

## If something is missing

- No Co-Invest connection: say so and point the user to the host's Co-Invest connector settings.
- `disable_paper_trading` is absent from the live list: this connection cannot leave paper mode. Say so and do not switch endpoints.
- The status read fails: do not place any order until the mode is known.
- Any other tool is absent: say this connection cannot do that, and do not switch endpoints or modes.
coinvest-portfolio-planning891 Bytes

View saved version →

---
name: coinvest-portfolio-planning
description: Review portfolio context and model allocations using read tools exposed by the connected Co-Invest service.
---

# Co-Invest portfolio planning

Use only portfolio and market data tools exposed by the connected Co-Invest service. Base planning on the user's stated goals and constraints. Ask for a material missing constraint when it changes the analysis; otherwise state the assumption clearly.

Separate returned holdings, balances, and other account facts from hypothetical allocations or recommendations. Do not treat a plan or proposal as an executed trade. Provide a trade review link only when the user explicitly requests one and an available tool actually returns it; never construct or guess a link. If required account data or a tool is unavailable, say so. Do not switch endpoints or use raw APIs to bypass the available tools.
coinvest-portfolio-review4.89 KB

View saved version →

---
name: coinvest-portfolio-review
description: "Review a Liquid account with Co-Invest: balances, account mode, open positions with TP/SL, resting orders, prediction positions, past trades and transfers, and allocation, in live or paper mode. Triggers on: show my portfolio, what are my positions, how am I doing, open orders, my PnL, trade history, recent activity, my account address. Read-only."
license: MIT
---

# Co-Invest portfolio review

Summarize the user's Liquid account from the connected Co-Invest tools, labeling every trading figure live or paper. Referral figures, and any balance whose description says it is real regardless of paper mode, are real account data. This skill is read-only and never switches mode, places or cancels anything.

## Workflow

1. Read the mode first with `paper_trading_status`, so every figure is labeled live or paper.
2. Call only what the question needs:
   - Balances, positions and TP/SL coverage: `get_portfolio`. Report each holding as the result types it: a position on `NVDA` or `xyz:NVDA` is a perpetual, not company shares, and an `EQ` token such as `EQNVDA` is a spot token. If the user asks about tokenized-stock tokens and the result does not list them, say the result did not show them, not that the user holds none.
   - Resting orders and TP/SL triggers: `view_open_orders`. Orders are not positions.
   - Prediction-market holdings: `view_prediction_positions`, unless `get_portfolio` already listed them; do not list a holding twice.
   - Past perpetual positions: `get_position_history`.
   - Trades, deposits, withdrawals and transfers as one timeline: `get_transaction_history`.
   - Allocation by notional, only when asked for a chart or breakdown: `show_portfolio_chart`.
   - The trading account address: `get_account`.
3. Present positions with side, size, entry, mark, unrealized PnL, leverage and liquidation price where returned. Keep holdings and orders in separate lists.

## Tools

- `get_portfolio`: current balances, account mode, positions and TP/SL coverage. Earn and staking balances are outside it.
- `view_open_orders`: resting perpetual limit orders and position-level TP/SL triggers. Where its description says so, it adds a protection-coverage readback and excludes prediction orders. For resting prediction orders, use `view_prediction_orders` with `status=open`.
- `get_position_history`: recent perpetual position lifecycles from a bounded fill window; `status` defaults to closed, `limit` 1 to 50 (default 10), `includeFills` adds up to 100 fills.
- `get_transaction_history`: newest-first timeline of fills, deposits, withdrawals, transfers and prediction trades; `limit` defaults to 10, max 100; `type` filters to trades, transfers or predictions.
- `show_portfolio_chart`: allocation by notional value.
- `view_prediction_positions`: prediction-market positions and outcome quantities.
- `paper_trading_status`: whether paper mode is on for this wallet or, where its description says so, that this connection is permanently paper-only.
- `get_account`: the public trading account address. It is not a deposit or bridge destination.
- `get_earn_balance`: Earn vault holdings, pending requests, APY and TVL, read-only, when the user asks about Earn.
- `get_staking`: HYPE staking balance and delegations, read-only, when the user asks what is staked.
- `refer`: the user's referral link and statistics, only when they ask for them.

## Rules

- Earn and staking balances are not in `get_portfolio`, and `get_transaction_history` does not list Earn vault activity. Read them with `get_earn_balance` and `get_staking` when the user asks and those tools are listed.
- History is recent coverage, not all-time. Say what window the result states. An `open` lifecycle means open at the last observed fill; use `get_portfolio` for the current position.
- While paper mode is on, trade and prediction rows are simulated. Deposit, withdrawal and transfer rows, where the result has them, are real wallet activity. 

Preview of the first 4,000 characters. Read full instructions →

coinvest-research4.59 KB

View saved version →

---
name: coinvest-research
description: "Research one named market or compare a few with Co-Invest: price, funding, open interest, smart-money positioning, technical indicators, order book, candles, and headlines for crypto, equity perpetuals, commodities, indices and other Liquid markets. Triggers on: analyze BTC, what is NVDA doing, how are traders positioned on gold, compare ETH and SOL, RSI for SOL, news on TSLA, read this link. Read-only."
license: MIT
---

# Co-Invest market research

Answer questions about one named asset, or a short comparison, with data returned by the connected Co-Invest tools. This skill is read-only: it never previews, proposes, places or changes anything.

## Workflow

1. Identify the asset or assets and the question: outlook, positioning, technicals, depth, news, or a pasted link.
2. Read the live tool list and schemas. Use only tools this connection exposes.
3. Call the narrowest tool that answers the question:
   - One known asset: `analyze_market` with its Liquid market symbol (for example `BTC`, `GOLD`, `NVDA`; keep a venue prefix such as `xyz:` exactly as given). If the user gave a name rather than a symbol, find the symbol with `search_markets` first. If no asset is clear, ask one short question. If the result asks for an asset choice, ask which candidate the user means and retry with that exact symbol.
   - Two to ten assets: one `analyze_markets_batch` call, not repeated single calls.
   - An unknown or partial name, or "can Liquid trade X": `search_markets` with that name as `query`. The no-query result lists only the top markets by volume, so absence there does not mean Liquid cannot trade it.
   - RSI, MACD, moving averages and similar: `get_technical_indicators`.
   - Depth, spread or candles, only on an explicit request: `show_orderbook`, `show_chart`.
   - Headlines: `get_news`. It takes no symbol and returns the current curated set for all markets, so report only headlines that name the asset and say when none do. A user-supplied URL: `read_link`.
4. Report what the tools returned, with the units, time or period they give. Keep returned data apart from your own interpretation, and name the instrument the result shows: an equity market such as `NVDA` or `xyz:NVDA` is a perpetual contract on the stock, not company shares; a commodity, index or crypto perpetual is not a stock; an `EQ` symbol such as `EQNVDA` is a tokenized-stock spot token.
5. Where the tool description asks for it, you may offer in one line to turn the analysis into a trade. Never call a proposal or order tool here; treat a yes as a separate trade request.

## Tools

- `analyze_market`: price, funding, open interest and positioning for one asset, including the smart-money versus losing-crowd split when available. Primary tool for a known asset.
- `analyze_markets_batch`: side-by-side price, funding and positioning for 2 to 10 symbols; an optional `thesis` frames the comparison.
- `get_technical_indicators`: indicator values from candles for one market; `interval` defaults to 1h.
- `show_chart`: candles and volume for one asset; `interval` is required (`1m`, `5m`, `15m`, `30m`, `1h`, `4h` or `1d`, no default), and `limit` defaults to 100, max 200.
- `show_orderbook`: bid and ask depth and spread for one asset.
- `get_news`: curated headlines with source links and an unusual-activity section (symbols with anomalously high last-hour volume).
- `read_link`: title and main text of a page the user supplied, or an X post if the server can read it; not for Liquid market or account data.
- `search_markets`: find a symbol or browse the top markets by volume.

## Rules

- Do not use `search_markets` for a symbol you already know.
- Re-fetch prices, funding and positioning for each new question; never reuse earlier numbers as current.
- Report returned data in text. Do not promise a chart or any visual; say what the result contained.
- Positioning describes positioning, not order book depth. Claim depth only from an order book 

Preview of the first 4,000 characters. Read full instructions →

coinvest-trade6.3 KB

View saved version →

---
name: coinvest-trade
description: "Place and manage Liquid perpetual trades the user explicitly asks for: market or limit orders, take-profit and stop-loss, closes, cancels and leverage changes, in live or paper mode, with a preview or a Liquid review link where this connection requires one. Triggers on: buy, sell, long, short, open a position, close my BTC, set a stop loss, set take profit, cancel my order, change leverage."
license: MIT
---

# Co-Invest trade

Turn an explicit perpetual-trade request into the right tool call for this connection. The live tool list and schemas decide how a write is gated.

## Workflow

1. Confirm the user asked for this action in this conversation, naming asset, side and size or the change. Research or a pick is not a request.
2. Read `paper_trading_status` and `get_portfolio` to label the order live or paper and size it against real balance and positions. Never toggle the mode for a trade.
3. Collect the terms. `size` is notional USD, which is margin times leverage; ask if a dollar amount is notional or margin. Leverage comes from the user. A limit order needs the user's price. Never raise a size silently.
4. Pick the path from the live schema:
   - **Executor whose description says it is internal or called only by a confirmation control:** never call it. Call the proposal tool it names (`suggest_trade`, `modify_position`, `get_portfolio` for a close) and report the returned terms. The change happens only when the user confirms the returned proposal with its own confirmation control; a typed "yes" in chat does not place it and the agent must not call the executor after one. With no such control shown, say this connection cannot place it from chat.
   - **Executor without `confirmed`:** it runs when called. State the action in one line, then call it once.
   - **Executor with `confirmed`:** preview, show the exact returned terms, and wait for the user's approval of those unchanged terms. Then call with `confirmed=true`.
   - **No executor in the tool list:** `suggest_trade` returns a review link. The user finishes in Liquid; nothing is placed from chat.
5. Report the returned status as given; accepted is not filled.

## Tools

- `suggest_trade`: proposal for one perpetual order, and the preview where `execute_order` has none. With no executor it returns a review link.
- `execute_order`: place the order. Where it takes `confirmed`, copy `executionMode` and the listed executor fields unchanged; never pass proposal-only fields such as `sizeBasis` or `markPrice`. Send `maxSlippageBps` (1 to 500) only where the schema has it and the description's executor field list does not omit it.
- `execute_tpsl`: set, update or remove TP/SL on an open position. Where it takes `confirmed`, preview with `modify_position`.
- `modify_position`: TP/SL proposal for an open position. Send the user's exact levels.
- `close_position`: close fully, or partially with `size` in coin units or, where the schema has it, `percent`. If it takes `confirmed`, preview first with it omitted or false, then resend the previewed coin size, or previewed percent when no size was returned. If its description says it is internal, never call it: call `get_portfolio` and point the user to its own controls, or say this connection cannot close from chat.
- `close_positions_batch`: close several positions. Preview first, then for partial closes resend `closes` with each returned `resolvedSize` (coin units) or previewed `percent`; for full closes send the exact previewed symbols (`symbols` always closes in full). Never send an empty selection: that means close every position.
- `cancel_order`: cancel a resting order by id from `view_open_orders`. One matching order: cancel it if the description says the request is the approval, else name it and cancel once the user approves. Several: ask which. Cancel once per request.
- `view_open_orders`: resting orders and TP/SL triggers. Prediction orders are not listed here.
- `update_leverage`: with

Preview of the first 4,000 characters. Read full instructions →

Package details

Publisher declarations from the archived package. These are separate from our research and the live service's terms.

Package author
Liquid

Package observed Nov 22, 2026.

Technical details
First seen
Sep 30, 2026 · 22:02 UTC
Last seen
Nov 22, 2026 · 12:00 UTC
Latest observed change
Nov 20, 2026 · 18:10 UTC
Collection status
Collected

plugin_asdk_app_6a20e26c6ab8819191519e2811e03522

Download plugin data (JSON)

Plugin details: served from cache. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.