Orderly Mcp

io.github.OrderlyNetworkPublished by GitHub account OrderlyNetworkv1.5.8Updated Nov 5, 2026

MCP Server for Orderly Network - Documentation and SDK patterns

VerifiedStreamable HTTPWeb executableFinanceKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Orderly Network documentation and SDK reference server that lets an assistant answer questions and guide developers building on Orderly's perpetual futures…

What you can do
  • Search bundled Orderly docs and SDK symbols (hooks, components, types, functions) by topic or question
  • Look up deployed smart contract addresses by chain, contract type and mainnet or testnet
  • Get step-by-step workflow guides for wallet connection, deposits, withdrawals, orders and take-profit/stop-loss
  • Retrieve reference docs for the trading REST and WebSocket APIs, Indexer API, Orderly One API, Strategy Vault API and Public Info API
  • Get build guides for Orderly SDK React components such as order entry, orderbook, positions and wallet connector
When to use it
Useful when building a trading front end or integration on Orderly Network and you want the assistant to pull accurate SDK patterns, contract addresses and API references instead of guessing. Also handy for answering conceptual questions about Orderly architecture, vaults, fees and order types.
Requirements
Either the hosted remote endpoint or the local npm package @orderly.network/mcp-server, which needs Node.js 18 or higher. No API keys or headers are declared for normal use; the NEAR AI API key mentioned in the README is only for regenerating the bundled data from source.
Before you install
The server is read-only reference material: it returns documentation, addresses and guides, not live trading actions. Bundled data can lag behind the official docs, so verify contract addresses and endpoints before using them in production. The optional data-regeneration scripts described in the README call paid AI services and require a NEAR AI API key.

Installation

In SourceWeft

  1. Open Orderly Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.OrderlyNetwork%2Forderly-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "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

Source: README.md at commit b24bf58

Tools

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.

Parameterslimitqueryrequiredscopedetail

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.

ParameterschainrequirednetworkcontractType

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.

Parametersworkflowrequired

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.

Parameterstyperequiredendpoint

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.

Parameterscategoryendpoint

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.

Parameterscomponentrequiredcomplexity

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.

Parameterscategoryendpoint

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.

Parameterscategoryendpoint

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.

ParameterscategoryqueryType

Version history

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

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts