Skip to content

SDKs & Tools

Xian ships tooling for three distinct jobs:

  • building and testing contracts
  • integrating applications and wallets
  • operating higher-level services around a Xian network

Core SDKs And Apps

ToolMain use
xian-clioperator CLI plus JSON-first wallet, query, and transaction automation
xian-jsTypeScript client, provider contract, relayer clients, and browser integration
xian-wallet-browserbrowser wallet extension and injected provider
xian-wallet-mobilemobile wallet application
xian-pyPython client, watchers, indexed reads, and relayer clients
xian-zkproving toolkit, shielded wallet model, bundle generation, local prover service
xian-intentkitagent-facing automation stack for Xian-native workflows
xian-dex-automationdeterministic DEX event automation service for rule-based trades

Developer Productivity Tools

ToolMain use
Playgroundsbrowser dapp example plus the dedicated contract playground
Contracting Hubcurated contract catalog, inspection, ratings, and deployment UI
Linterstatic validation for contract source before deployment
MCP Serverlocal AI-assistant bridge for wallets, reads, submissions, and DEX flows

Common Install Paths

TypeScript / browser tooling:

bash
npm install @xian-tech/client @xian-tech/provider

Python application SDK:

bash
uv add xian-tech-py

CLI automation and operator tooling:

bash
uv tool install xian-tech-cli

Local contract runtime and testing:

bash
uv add xian-tech-contracting

Shielded proving toolkit:

bash
uv add xian-tech-zk

How To Choose

  • use xian-tech-contracting when you are writing or testing contracts
  • use xian-cli when you want shell-first automation or operator workflows
  • use xian-py or xian-js when you are building apps, services, wallets, or library-level integrations
  • use xian-zk when you are working with shielded-note or shielded-command flows
  • use xian-dex-automation when a DEX rule should execute predictably without an AI model deciding the action
  • use the hub, playground, or MCP server when you want a higher-level developer surface instead of starting from raw SDK calls