Orderly Mcp

io.github.OrderlyNetwork由 GitHub 帳號 OrderlyNetwork 發布v1.5.8更新於 Nov 5, 2026

MCP Server for Orderly Network - Documentation and SDK patterns

已驗證Streamable HTTP可網頁執行金融知識與記憶開發者工具

概覽

AI 產生的概覽

Orderly Network 文件與 SDK 參考伺服器,讓助理回答相關問題並協助開發者以 Orderly 永續合約基礎設施進行開發。

可以做什麼
  • 依主題或問題檢索內建的 Orderly 文件與 SDK 符號(hooks、元件、型別、函式)
  • 依鏈、合約類型以及主網或測試網查詢已部署的智慧合約位址
  • 取得錢包連接、入金、出金、下單及停利停損等逐步工作流程指南
  • 查閱交易 REST 與 WebSocket API、Indexer API、Orderly One API、Strategy Vault API 與 Public Info API 的參考文件
  • 取得下單、委託簿、持倉、錢包連接器等 Orderly SDK React 元件的建置指南
適用情境
適合在以 Orderly Network 建置交易前端或整合時使用,讓助理直接取得正確的 SDK 用法、合約位址與 API 參考,而不是憑空猜測。也適合回答關於 Orderly 架構、金庫、費用與訂單類型的概念性問題。
執行需求
可使用託管的遠端端點,或本機 npm 套件 @orderly.network/mcp-server,後者需要 Node.js 18 或以上版本。一般使用未宣告需要 API 金鑰或請求標頭;README 提到的 NEAR AI API 金鑰僅用於從來源重新產生內建資料。
安裝前請注意
此伺服器僅提供唯讀參考資料,回傳文件、位址與指南,不會執行實際交易操作。內建資料可能落後於官方文件,在正式環境使用合約位址與端點前請先確認。README 中選用的資料重新產生腳本會呼叫付費 AI 服務,並需要 NEAR AI API 金鑰。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Orderly Mcp,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/io.github.OrderlyNetwork%2Forderly-mcp/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "orderly": {
      "type": "http",
      "url": "https://mcp.orderly.network/"
    }
  }
}

README

Orderly Network MCP Server

A Model Context Protocol (MCP) server providing documentation and SDK patterns for Orderly Network - an omnichain perpetual futures trading infrastructure.

Quick Start

Install the MCP server with one command for your AI client:

bash
npx @orderly.network/mcp-server init --client <client>

Supported clients: claude, cursor, vscode, codex, opencode

Examples

bash
# OpenCodenpx @orderly.network/mcp-server init --client opencode
# Claude Codenpx @orderly.network/mcp-server init --client claude
# Cursornpx @orderly.network/mcp-server init --client cursor
# VS Code (with Copilot)npx @orderly.network/mcp-server init --client vscode
# Interactive mode (prompts for client selection)npx @orderly.network/mcp-server init

This command will:

  1. Create the appropriate configuration file for your AI client
  2. Install @orderly.network/mcp-server as a dev dependency
  3. Guide you through the next steps

After installation: Restart your AI client and try asking: "How do I connect to Orderly Network?"


What This Server Provides

This MCP server enables AI assistants to answer questions about Orderly Network and guide developers in building React components using the Orderly SDK v2.

Features

  • Documentation Search: Query Orderly docs for architecture, APIs, and concepts
  • SDK Patterns: Get code examples for all v2 hooks (useOrderEntry, usePositionStream, etc.)
  • Contract Addresses: Lookup smart contract addresses for all supported chains
  • Workflow Guides: Step-by-step explanations of common development tasks
  • Component Guides: Patterns for building trading UI components
  • API Reference: REST and WebSocket endpoint documentation
  • Indexer API: Trading metrics, account events, trades, and volume statistics
  • Orderly Predict: 5-minute BTC Up/Down rounds, order rules, settlement, fees, and SDK integration (covered by documentation search)

Installation

Quick Install (Recommended)

Use the CLI to automatically configure your AI client:

bash
npx @orderly.network/mcp-server init --client <client>

Available clients:

ClientCommandConfig Location
Claude Code--client claude.mcp.json
Cursor--client cursor.cursor/mcp.json
VS Code--client vscode.vscode/mcp.json
Codex--client codex~/.codex/config.toml
OpenCode--client opencode.opencode/mcp.json

Manual Setup

If you prefer to configure manually or the automatic setup doesn't work for your client:

Prerequisites
  • Node.js 18 or higher
  • Yarn (or npm)
Setup from Source
  1. Clone or create the project:
bash
cd orderly-mcp
  1. Install dependencies:
bash
yarn install
  1. Build the project:
bash
yarn build

Hosted Server

A publicly hosted instance is available at https://mcp.orderly.network.

Health check:

bash
curl https://mcp.orderly.network/health

Use in MCP client config (Streamable HTTP):

json
{  "mcpServers": {    "orderly": {      "url": "https://mcp.orderly.network/"    }  }}

Running the Server

The MCP server supports two modes:

1. Stdio Mode (Default - for local MCP clients)

Use this for local AI assistants:

bash
yarn start
Manual Configuration

If not using the automatic installer, add this configuration to your AI client:

Claude Code (.mcp.json):

json
{  "mcpServers": {    "orderly": {      "command": "npx",      "args": ["@orderly.network/mcp-server@latest"]    }  }}

Cursor (.cursor/mcp.json):

json
{  "mcpServers": {    "orderly": {      "command": "npx",      "args": ["@orderly.network/mcp-server@latest"]    }  }}

VS Code (.vscode/mcp.json):

json
{  "servers": {    "orderly": {      "command": "npx",      "args": ["@orderly.network/mcp-server@latest"]    }  }}

OpenCode (.opencode/mcp.json):

json
{  "$schema": "https://opencode.ai/config.json",  "mcp": {    "orderly": {      "type": "local",      "command": ["npx", "@orderly.network/mcp-server@latest"],      "enabled": true    }  }}

Codex (~/.codex/config.toml):

toml
[mcp_servers.orderly]command = "npx"args = ["@orderly.network/mcp-server@latest"]
2. HTTP Mode (for self-hosted deployments)

Run as an HTTP server for remote access:

bash
yarn start:http

The server will start on port 3000 (or PORT env var):

  • MCP endpoint: http://localhost:3000/
  • Health check: http://localhost:3000/health

Note: A public instance is already deployed at https://mcp.orderly.network - see Hosted Server above.

Docker Deployment:

bash
# Build the imagedocker build -t orderly-mcp .
# Run the containerdocker run -p 3000:3000 orderly-mcp

The Docker image runs in stateless HTTP mode by default.

Development

For development with auto-rebuild:

bash
yarn dev

Code Quality

This project uses ESLint and Prettier for code quality:

bash
# Run lintingyarn lint
# Fix linting issuesyarn lint:fix
# Format codeyarn format
# Check formattingyarn format:check
# Type checkyarn typecheck

Available Tools

1. search_orderly_docs

Search Orderly documentation for specific topics, concepts, or questions.

Parameters:

  • query (string, required): Search query about Orderly
  • limit (number, optional): Maximum results (default: 5)

Example queries:

  • "how does the vault work"
  • "trading fees"
  • "order types"
  • "leverage calculation"

SDK symbols (hooks, types, components, functions) are now surfaced inline by search_orderly_docs — see SDK symbol search below.

2. get_contract_addresses

Get smart contract addresses for Orderly on specific chains.

Parameters:

  • chain (string, required): Chain name (e.g., 'arbitrum', 'optimism', 'base')
  • contractType (string, optional): Contract type or 'all' (default: 'all')
  • network (string, optional): 'mainnet' or 'testnet' (default: 'mainnet')

Supported chains:

  • EVM: ethereum, arbitrum, optimism, base, mantle, solana
  • Orderly L2: orderlyL2

3. explain_workflow

Get step-by-step explanation of common development workflows.

Parameters:

  • workflow (string, required): Workflow name

Available workflows:

  • wallet connection: Connect wallet and create an Orderly key
  • place first order / limit order: Create, track, edit, and cancel an order
  • deposit: Approve and deposit through the Vault contract
  • withdraw: Sign the EIP-712 withdrawal and submit it
  • set tp sl: Create bracket take-profit/stop-loss orders

4. get_api_info

Get information about Orderly REST API or WebSocket streams.

Parameters:

  • type (string, required): 'rest', 'websocket', or 'auth'
  • endpoint (string, optional): Specific endpoint or stream name

5. get_indexer_api_info

Get information about Orderly Indexer API for trading metrics, account events, trades, and volume statistics (rankings endpoints available via endpoint search).

Parameters:

  • endpoint (string, optional): Specific endpoint path or name (e.g., '/events_v2', 'daily_volume', 'ranking/positions')
  • category (string, optional): Filter by category (e.g., 'trading_metrics', 'events::events_api', 'trades::trades_api')

Available categories:

  • Trading Metrics: Daily volume, fees, perp trading data (/daily_volume, /daily_trading_fee, /daily_orderly_perp)
  • Events: Account events with pagination (/events_v2) - trades, settlements, liquidations, transactions
  • Volume Statistics: Account and broker volume stats (/get_account_volume_statistic, /get_broker_volume_statistic)
  • Trades: Trade data with filters (/trades)

Rankings (no category; search by endpoint):

  • Positions, PnL, trading volume, deposits/withdrawals (/ranking/positions, /ranking/realized_pnl, /ranking/trading_volume, /ranking/deposit, /ranking/withdraw)

Example:

# Get all indexer API endpointsget_indexer_api_info
# Get specific endpoint detailsget_indexer_api_info endpoint="/events_v2"
# Get all endpoints in a categoryget_indexer_api_info category="trading_metrics"

6. get_component_guide

Get guidance on building React UI components using Orderly SDK.

Parameters:

  • component (string, required): Component type
  • complexity (string, optional): 'minimal', 'standard', or 'advanced' (default: 'standard')

Available guides: TradingPage, OrderBook, OrderEntryWidget, OrderEntry, PositionsWidget, WalletConnectorWidget.

Other components return a pointer to search_orderly_docs (scope sdk).

7. get_orderly_one_api_info

Get information about Orderly One API for DEX creation, graduation, and management.

Parameters:

  • endpoint (string, optional): Specific endpoint path or name (e.g., '/dex', 'verify-tx', '/theme/modify')
  • category (string, optional): Filter by category (e.g., 'auth', 'dex', 'graduation', 'theme', 'stats', 'leaderboard', 'admin')

Available categories:

  • auth: Wallet signature-based authentication (nonce, verify, validate)
  • dex: DEX management - create, update, delete, deploy, and manage exchanges
  • graduation: Graduation system - upgrade from demo to full broker with fee splits
  • theme: AI-powered theme generation and CSS customization
  • stats: Platform-wide statistics and analytics
  • leaderboard: DEX rankings, performance metrics, and leaderboards
  • admin: Administrative operations for platform management

Example:

# Get overview and authentication flowget_orderly_one_api_info
# Get all endpoints in a categoryget_orderly_one_api_info category="dex"get_orderly_one_api_info category="graduation"
# Get specific endpoint detailsget_orderly_one_api_info endpoint="verify-tx"get_orderly_one_api_info endpoint="/theme/modify"

Available Resources

Access comprehensive documentation via resource URIs. All resources support fuzzy search with pagination:

Query Parameters:

  • search (required) - Fuzzy search query
  • page (optional) - Page number (default: 1)
  • limit (optional) - Results per page, max 10 (default: 10)

Resources:

  • orderly://overview - High-level protocol architecture (no search required)
  • orderly://sdk/hooks?search=orderEntry - Search SDK hooks by name, description, or category
  • orderly://sdk/components?search=Checkbox - Search components by name or description
  • orderly://contracts?search=arbitrum - Search contracts by chain or name
  • orderly://workflows?search=wallet - Search workflows by name or steps
  • orderly://api/rest?search=position - Search REST API endpoints
  • orderly://api/websocket?search=orderbook - Search WebSocket streams
  • orderly://api/indexer?search=events - Search Indexer API endpoints

Example:

orderly://sdk/hooks?search=useOrderEntry&page=1&limit=5

Example Usage

Searching Documentation

User: "How does Orderly's vault system work?"
AI uses search_orderly_docs with query "vault system"→ Returns explanation of cross-chain vault architecture

Searching SDK Symbols

User: "Show me how to use useOrderEntry"
AI uses search_orderly_docs with query "useOrderEntry"→ Returns inline SDK hook record: signature, params, returns, source path

Looking Up Contracts

User: "What's the USDC address on Arbitrum?"
AI uses get_contract_addresses with chain "arbitrum", contractType "USDC"→ Returns contract address

Explaining Workflows

User: "How do I place my first order?"
AI uses explain_workflow with workflow "place first order"→ Returns step-by-step guide

Component Building Guide

User: "How do I build an order entry component?"
AI uses get_component_guide with component "order-entry"→ Returns complete implementation guide

Data Sources

This MCP server includes embedded data from:

  1. Orderly Documentation: Architecture, concepts, and guides
  2. SDK Patterns: v2 hook examples and patterns from @orderly.network/hooks
  3. DEX Examples: Complete working components from the example-dex repository
  4. Contract Addresses: All deployed contracts across supported chains
  5. API Specifications: REST and WebSocket endpoints
  6. Indexer API: Trading metrics, account events, trades, and volume statistics
  7. Orderly One API: DEX creation, graduation, and management API documentation
  8. Workflow Guides: Common development task explanations
  9. Orderly Predict: Round lifecycle, order rules, settlement, fee schedule, and SDK integration

Project Structure

orderly-mcp/├── src/│   ├── index.ts                 # Main server entry (stdio mode)│   ├── http-server.ts           # HTTP server entry (stateless mode)│   ├── server.ts                # Shared MCP server logic│   ├── tools/│   │   ├── searchDocs.ts        # Unified doc + SDK symbol search│   │   ├── contracts.ts         # Contract address lookup│   │   ├── workflows.ts         # Workflow explanations│   │   ├── apiInfo.ts           # API documentation│   │   ├── indexerApi.ts        # Indexer API documentation│   │   ├── componentGuides.ts   # Component building guides│   │   ├── orderlyOneApi.ts     # Orderly One API documentation│   │   ├── svApi.ts             # Strategy Vault API documentation│   │   └── publicInfoApi.ts     # Public Info API documentation│   ├── resources/│   │   └── index.ts             # Resource handlers│   └── data/│       ├── documentation.json   # Searchable documentation chunks│       ├── sdk-symbols.json     # Type-accurate SDK symbols (hooks/types/components/functions)│       ├── contracts.json       # Contract addresses│       ├── workflows.json       # Workflow explanations│       ├── api.json             # API specifications│       ├── indexer-api.json     # Indexer API documentation│       ├── orderly-one-api.json # Orderly One API documentation│       ├── sv-api.json          # Strategy Vault API documentation│       ├── public-info-api.json # Public Info API documentation│       ├── component-guides.json # Component guides│       └── resources/│           └── overview.md      # Protocol overview├── .vscode/                     # VS Code settings│   ├── settings.json│   └── extensions.json├── package.json├── tsconfig.json├── eslint.config.mjs            # ESLint configuration├── .prettierrc                  # Prettier configuration├── .gitignore├── .dockerignore                # Docker ignore rules├── Dockerfile                   # Docker build configuration└── README.md

Updating Data

All data files in src/data/ are auto-generated via scripts in the scripts/ folder. Do not edit JSON files manually - they will be overwritten when regeneration scripts run.

Quick Free Refresh

Refresh all OpenAPI-sourced data (no AI calls, no API keys, internet only):

bash
yarn update:free

This runs: generate_api_from_openapi, generate_indexer_api, generate_sv_api, generate_contracts, and generate_orderly_one_api, then builds and tests.

Prerequisites

  1. NEAR AI API key in .env file: NEAR_AI_API_KEY=your_key
  2. Get API key at: https://cloud.near.ai/api-keys

Complete Regeneration (Recommended)

Generate everything from scratch:

bash
# 1. (Optional) Process Telegram export — 2 steps with manual review betweennode scripts/clean_telegram_export.js    # 🆓 free, filter → telegram_chats_filtered/# ...review + delete unwanted files manually...node scripts/analyze_telegram_chats.js      # 💰 costs money → tg_analysis.json
# 2. Analyze docs → docs_analysis.json                                 💰 costs money#    (clones OrderlyNetwork/documentation-public automatically)node scripts/analyze_docs.js
# 3. Get type-accurate SDK symbols from npm                            🆓 freenode scripts/generate_sdk_symbols.js
# 4. Get component-building guides from SDK source                      🆓 freenode scripts/analyze_sdk.js
# 5. Generate documentation and workflows                              💰 costs moneynode scripts/generate_mcp_data.js
# 6. Generate API docs from OpenAPI spec                               🆓 freenode scripts/generate_api_from_openapi.js
# 7. Generate Indexer API docs from OpenAPI spec                       🆓 freenode scripts/generate_indexer_api.js
# 8. Generate Orderly One API docs from OpenAPI spec                   🆓 freenode scripts/generate_orderly_one_api.js
# 9. Generate contract addresses                                       🆓 freenode scripts/generate_contracts.js
# 10. Build and testyarn build && yarn test:run

Update Only Documentation

Refresh from official docs (uses git-cloned repo as source):

bash
# 1. Analyze docs only (clones repo automatically)                     💰 costs moneynode scripts/analyze_docs.js
# 2. Generate                                                           💰 costs moneynode scripts/generate_mcp_data.js
# 3. Buildyarn build

Data Files

FileSourceGeneration Script
documentation.jsonOfficial docs (git: documentation-public)generate_mcp_data.js
sdk-symbols.json@orderly.network/sdk-docs npm packagegenerate_sdk_symbols.js
component-guides.jsonHand-written, checked against @orderly.network/* 3.3.1—
workflows.jsonOfficial docs (git: documentation-public)generate_mcp_data.js
api.jsonOpenAPI specgenerate_api_from_openapi.js
indexer-api.jsonIndexer API OpenAPI specgenerate_indexer_api.js
orderly-one-api.jsonOrderly One OpenAPI specgenerate_orderly_one_api.js
sv-api.jsonStrategy Vault OpenAPI specgenerate_sv_api.js
public-info-api.jsonPublic Info API MDX docsgenerate_public_info_api.js
contracts.jsonOfficial docs (Git: documentation-public)generate_contracts.js

Contributing

To add new content, you need to update the source data and regenerate:

  1. New Documentation: Update documentation-public repo (or Telegram exports), then run generation scripts
  2. New SDK Pattern: The SDK is auto-parsed from GitHub - patterns appear automatically when SDK updates
  3. New DEX Examples: Clone the example-dex repo and run the analysis scripts
  4. New Chain: Update source documentation, then regenerate
  5. New Workflow: Add to source docs or Telegram chats, then regenerate

License

MIT

Support

來源:README.md,提交 b24bf58

工具

9

search_orderly_docs

Search Orderly Documentation

Search bundled Orderly docs and SDK symbols by topic or question. Returns up to `limit` ranked Markdown results with relevance scores: `scope: 'sdk'` returns hooks/components/types/functions with signatures, props, and source paths; `'docs'` returns prose; `'auto'` (default) picks the corpus from the query. Use `'sdk'` for exact symbol signatures and `detail: 'full'` only when the summary is insufficient, since it returns much longer text. Read-only local search — no network calls, credentials, rate limits, or side effects. Use for open-ended discovery when the component, workflow, or endpoint is unknown; for a known component use get_component_guide, for a task walkthrough use explain_workflow, for an endpoint use get_api_info, get_indexer_api_info, get_public_info_api_info, or get_strategy_vault_api_info, and for addresses use get_contract_addresses.

輸入參數limitquery必填scopedetail

get_contract_addresses

Get Orderly Contract Addresses

Get the deployed smart contract addresses for Orderly on a specific chain and network. `chain` is required; `contractType` filters to one contract (e.g. vault, usdc, usdt) or 'all'; `network` selects mainnet (default) or testnet. 'all' lists every contract with an address on the selected network; a specific type also returns its description and the address on the other network when available. Unknown chains or contract types return the valid options. Read-only lookup from bundled data — no network calls, credentials, or side effects. Use for deployment and wiring addresses only; for API details use get_api_info or the matching named API tool, for SDK symbols use search_orderly_docs, and for integration steps use explain_workflow.

輸入參數chain必填networkcontractType

explain_workflow

Explain Orderly Workflow

Get a curated, step-by-step guide for a common Orderly development task such as wallet connection, deposits, SDK setup, or placing orders. Returns exactly one best-matching workflow as Markdown with prerequisites, numbered steps, TypeScript examples, common issues, and related workflows; pass the task in natural language or a partial name, and a miss lists available workflows. Read-only lookup from bundled data — no network calls, credentials, rate limits, or side effects. Use for end-to-end tasks, not one-off lookups: get_component_guide for a known UI component, search_orderly_docs (scope 'sdk') for symbols, get_api_info for core endpoints, and the matching named tool for Indexer, Public Info, Orderly One, or Strategy Vault data.

輸入參數workflow必填

get_api_info

Get Orderly API Info

Get reference documentation for the core Orderly trading API: REST endpoints, WebSocket streams, or authentication. For `rest` or `websocket`, omitting `endpoint` lists every endpoint or stream with base URLs and auth requirements; supplying `endpoint` fuzzy-matches one item and returns its method/path or topic, auth, rate limits, parameters, message formats, and a TypeScript example. `type: 'auth'` returns the signing flow and ignores `endpoint`. Read-only bundled docs — it does not call the API and requires no credentials, rate limits, or side effects. Use `type` alone to discover valid names, then `endpoint` for detail; for historical analytics use get_indexer_api_info, for zero-auth public data use get_public_info_api_info, for DEX management use get_orderly_one_api_info, and for vault data use get_strategy_vault_api_info.

輸入參數type必填endpoint

get_indexer_api_info

Get Indexer API Info

Get reference documentation for the Orderly Indexer API, a read-only source of historical and aggregated trading data: volume and fee metrics, account events, trades, and rankings. Omit both parameters for an overview with base URLs, categories, common errors, and usage tips; pass `category` to discover all endpoints in an area, or `endpoint` to fuzzy-match one endpoint and return its parameters, request/response schemas, and TypeScript example (category takes precedence if both are supplied). Bundled docs lookup only — no API call, credentials, or rate limits. Use for analytics, dashboards, account history, and leaderboards; for live trading operations use get_api_info, and for zero-auth market data use get_public_info_api_info.

輸入參數categoryendpoint

get_component_guide

Get Orderly Component Guide

Get a curated build guide for a React UI component from the Orderly SDK, such as order-entry, orderbook, positions, or wallet-connector. Returns Markdown with required packages, key hooks, a complete TSX example, tips, styling notes, common mistakes, and related components; `complexity` selects the example depth — 'minimal' for a scaffold, 'advanced' for production wiring — and falls back to 'standard'. Guides include full code and can be long; a miss lists available guides and points to search_orderly_docs. Read-only static guidance — no network calls, credentials, rate limits, or side effects. Use for a known UI component; for SDK hook/type signatures use search_orderly_docs (scope 'sdk'), for end-to-end steps use explain_workflow, and for backend endpoints use get_api_info or the matching domain API tool.

輸入參數component必填complexity

get_orderly_one_api_info

Get Orderly One API Info

Get reference documentation for the Orderly One API used to create, graduate, and manage a DEX, covering auth, DEX, graduation, theme, stats, leaderboard, and admin endpoints. Omit both parameters for an overview; pass `category` to discover all endpoints in an area, or `endpoint` to fuzzy-match one endpoint and return its method, parameters, and examples (category takes precedence if both are supplied). Responses flag agent-blocked or conditional operations such as DEX creation, deployment, and deletion. Read-only bundled docs — it never calls the API or requires credentials. Use for Orderly One/DEX-builder tasks; for core trading use get_api_info, for vault data use get_strategy_vault_api_info, and for analytics use get_indexer_api_info or get_public_info_api_info.

輸入參數categoryendpoint

get_strategy_vault_api_info

Get Strategy Vault API Info

Get reference documentation for the Orderly Strategy Vault REST API covering vault performance, strategy providers, fund management, liquidity providers, and user stats. Omit both parameters for an overview with base URL and categories; pass `category` to discover all endpoints in an area, or `endpoint` to fuzzy-match one endpoint and return its full detail (category wins if both are supplied). Read-only bundled docs — it does not call the API and requires no credentials or rate limits. Use for vault/yield integrations; for core trading use get_api_info, for historical analytics use get_indexer_api_info, and for zero-auth market data use get_public_info_api_info.

輸入參數categoryendpoint

get_public_info_api_info

Get Public Info API Info

Get reference documentation for the Orderly Public Info API — a zero-auth single endpoint (POST /v1/public/query) for market, account, and platform data selected by a `type` field. Covers 24 query types (marketSummary, accountState, orderbook, candles, topAddresses, whaleContext, etc.); `queryType` accepts exact, partial, or fuzzy names and returns params, response fields, example, weight, and freshness; `category` lists a group (queryType wins if both are supplied); omit both for the overview and rate-limit rules. Read-only bundled docs — it does not call the endpoint. Use instead of get_api_info for zero-auth public data; use get_api_info for authenticated trading, get_indexer_api_info for historical analytics, and get_strategy_vault_api_info for vault data.

輸入參數categoryqueryType

版本歷史

4
  1. v1.5.8最新Nov 5, 2026
  2. v1.5.7Nov 3, 2026
  3. v1.5.5Oct 29, 2026
  4. v1.1.1Sep 16, 2026

評分

已滿足適用檢查項的 100%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分