API Documentation

Overview

Arsenal skills are server-side execution units, not text descriptions. Each skill is real TypeScript code running on Arsenal's servers — making live on-chain RPC calls, invoking protocol SDKs, and building ready-to-sign transactions. Your agent sends a request; Arsenal handles all the blockchain complexity and returns structured data.

This is different from text-based skill formats (like Anthropic's SKILL.md) where the agent itself has to figure out the implementation. With Arsenal, execution is Arsenal's job — the agent only decides what to do, not how.

https://arsenal.sumplus.xyz

Skill Architecture

Arsenal skills are server-side code executors, not text prompts. Each skill is a TypeScript function that runs on Arsenal's servers — it makes real on-chain RPC calls, invokes protocol SDKs, builds unsigned transactions, and returns structured data back to the agent.

Two layers, two jobs

Why code, not text prompts?

Available Skills

Arsenal-hosted skills run in-process — no separate server, no API key needed beyond your Arsenal token. Ethereum mainnet skills require ALCHEMY_API_KEY on the server (already configured).

Ethereum Mainnet (P0)

Bridge (Cross-chain, P0)

Multi-chain EVM

Sui / Solana / Other

Cetus CLMM, Bluefin Ember, Aftermath Finance, NAVI, Scallop, Suilend, IKA dWallet (Sui) · Monad (parallel-EVM L1, chain 143 — chain toolkit: balances/gas/transfers/MON⇄WMON wrap + Uniswap V3 swap quotes/build) · Jupiter, Raydium (AMM/CLMM swap + build_swap_tx), Meteora (largest Solana liquidity layer — DLMM data + Meteora-routed swap), Orca Whirlpools, Kamino Finance (largest Solana lending + automated vaults — deposit/withdraw/borrow/repay), Jito (jitoSOL liquid staking + MEV tip floor — stake/unstake), Jupiter Perpetuals (SOL/ETH/BTC perps — open/close leveraged positions) (Solana) · dYdX, Hyperliquid (#1 perps — market data + build_order/build_cancel_order: sign-and-submit client-side), GMX, WEEX, Binance (CEX spot — public market data + signed trading with your own API key), Binance Stock Perpetuals (USDⓈ-M TradFi perps — stocks/ETFs/commodities price + funding rates), Binance bStocks (tokenized-equity product info) · Tempo MPP, Token Info · Polymarket · Sumplus Yield Optimizer · DAOaaS Swap (Eniac Network, chain 173) · Arc Chain (Circle Arc Testnet, USDC-native L1, chain 5042002) · Exchange OS (OKX X Layer pre-launch toolkit, chain 196 — native OKB / WOKB primitives, venue + TradeZone actions land when contracts publish) · SafeRouter Verified Inference (confidential-verifiable LLM gateway with per-request TEE attestation — read-only discovery, Arsenal never proxies the chat path)

Use GET /api/skills?search=... to discover all available skills and their full schemas.

Authentication

Browsing skills is public. All write and execute endpoints require a Bearer token. Two token types are accepted:

• Supabase JWT — from /api/auth/login
• API Key — from /api/auth/signup (returned on signup) or /api/auth/apikey — recommended for agents, does not expire

curl -H 'Authorization: Bearer YOUR_API_KEY' https://arsenal.sumplus.xyz/api/skills

const res = await fetch('/api/skills', {
  headers: {
    'Authorization': 'Bearer ' + apiKey,
  }
});

REST API

curl 'https://arsenal.sumplus.xyz/api/skills?category=Blockchain&limit=10' \
  -H 'Authorization: Bearer YOUR_API_KEY'

curl 'https://arsenal.sumplus.xyz/api/skills/SKILL_ID' \
  -H 'Authorization: Bearer YOUR_API_KEY'

curl -X POST 'https://arsenal.sumplus.xyz/api/execute' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"skill_id": "SKILL_ID", "input": {"address": "0x..."}}'

const result = await fetch('/api/execute', {
  method: 'POST',
  headers: {
    'Authorization': 'Bearer ' + apiKey,
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    skill_id: 'SKILL_ID',
    input: { address: '0x...' },
  }),
});
const data = await result.json();

Publish Skills

Any authenticated user or agent can publish community skills. New skills start with status: pending and become visible after admin approval. Official skills (author_type: official) are approved immediately.

Publish a new skill:

curl -X POST 'https://arsenal.sumplus.xyz/api/skills' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{
    "name": "My Skill Name",
    "description": "What this skill does, in detail.",
    "category": "Blockchain",
    "tags": ["defi", "ethereum"],
    "version": "1.0.0",
    "schema": {
      "input": {
        "type": "object",
        "properties": {
          "address": { "type": "string", "description": "Wallet address" }
        },
        "required": ["address"]
      },
      "output": {
        "type": "object",
        "properties": {
          "balance": { "type": "string" }
        }
      }
    },
    "code": "// implementation or pseudocode here",
    "usage_examples": [
      {
        "title": "Get balance",
        "input": { "address": "0xabc..." },
        "expected_output": { "balance": "1.5 ETH" }
      }
    ],
    "is_paid": false
  }'

On success, returns { skill: { id, name, status } }. Save the id— you'll need it to update or reference the skill.

Update an existing skill (author or admin only):

curl -X PUT 'https://arsenal.sumplus.xyz/api/skills/SKILL_ID' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{
    "description": "Updated description",
    "tags": ["defi", "ethereum", "v2"]
  }'

MCP Interface

Full Model Context Protocol support. Three methods: skills/list, skills/get, skills/execute.

Claude Code configuration:

{
  "mcpServers": {
    "sumplus": {
      "url": "https://arsenal.sumplus.xyz/mcp",
      "apiKey": "YOUR_API_KEY"
    }
  }
}

List skills:

POST /mcp
Content-Type: application/json
Authorization: Bearer YOUR_API_KEY

{
  "method": "skills/list",
  "params": { "category": "Blockchain", "limit": 10 }
}

Execute a skill:

POST /mcp
Content-Type: application/json
Authorization: Bearer YOUR_API_KEY

{
  "method": "skills/execute",
  "params": {
    "skill_id": "SKILL_ID",
    "input": { "address": "0x..." }
  }
}

Function Calling

Fetch OpenAI-compatible function definitions and pass them directly to any LLM that supports tool use.

Fetch function definitions:

GET /api/functions?category=Blockchain
Authorization: Bearer YOUR_API_KEY

# Returns OpenAI-compatible function definitions array

Example function definition returned:

{
  "name": "sui_blockchain_toolkit",
  "description": "Interact with the SUI blockchain network",
  "parameters": {
    "type": "object",
    "required": [
      "action",
      "address"
    ],
    "properties": {
      "action": {
        "type": "string",
        "enum": [
          "get_balance",
          "get_tokens",
          "get_nfts"
        ]
      },
      "address": {
        "type": "string",
        "description": "SUI wallet address (0x...)"
      }
    }
  }
}

Execute via POST /api/functions/execute with { "function_name": "sui_blockchain_toolkit", "arguments": { ... } }

Router

The unified router endpoint lets agents search, get, and execute skills through a single API. No skill installation needed — Arsenal acts as the router for all capabilities.

Search:

POST /api/router
Content-Type: application/json
Authorization: Bearer YOUR_API_KEY

{
  "action": "search",
  "query": "SUI blockchain balance"
}

Execute:

POST /api/router
Content-Type: application/json
Authorization: Bearer YOUR_API_KEY

{
  "action": "execute",
  "skill_id": "SKILL_ID",
  "input": { "action": "get_balance", "address": "0x..." }
}

Talus Nexus Gateway

Arsenal wraps a subset of its Sui skills as Talus Nexus off-chain tools so any Nexus DAG workflow can call Arsenal skills as native tool nodes. Each wrapped skill lives at /api/tools/<slug> and exposes the three standard Nexus endpoints: GET /health, GET /meta, POST /invoke.

No API key needed — Nexus Leader nodes authenticate at the application layer via signed HTTP (Ed25519), which is post-MVP. Today the gateway runs un-signed over HTTPS.

Tools advertised for Nexus testnet registration:

The testnet tool pins every invocation to Sui testnet and restricts Cetus Aggregator providers to CETUS and DEEPBOOKV3 (the DEXes with live Sui testnet deployments). No mainnet RPC is reachable through it.

Mainnet-only tools (reachable individually, not in batch index):

These tools call Sui mainnet RPC. They stay reachable for inspection but are withheld from the batch index to prevent testnet DAGs from accidentally triggering mainnet transactions. Non-Sui skills (EVM / Solana / XLayer / Tempo) are not exposed at all — Talus Nexus only supports Sui today.

Batch index for Nexus CLI --batch:

GET /api/tools?network=testnet

# Returns Nexus tools ready for testnet registration
{
  "network": "testnet",
  "tools": [
    { "fqn": "xyz.sumplus.cetus-testnet@1", "url": "https://arsenal.sumplus.xyz/api/tools/cetus-testnet" }
  ]
}

Tool definition (/meta):

GET /api/tools/navi/meta

{
  "fqn": "xyz.sumplus.navi@1",
  "type": "offchain",
  "url": "https://arsenal.sumplus.xyz/api/tools/navi",
  "description": "NAVI is the leading lending & borrowing protocol on Sui...",
  "input_schema":  { "$schema": "...", "type": "object", "required": ["action"], "properties": { ... } },
  "output_schema": { "$schema": "...", "oneOf": [ { "properties": { "ok":  { "type": "object" } } },
                                                  { "properties": { "err": { "type": "object" } } } ] }
}

Note: Nexus requires output_schema top-level to be oneOf — DAG edges route off variants.

Invocation (/invoke):

POST /api/tools/navi/invoke
Content-Type: application/json

{ "action": "get_markets" }

# → { "ok":  { "protocol": "NAVI Protocol", "markets": [...] } }
# or  { "err": { "reason": "..." } }

Responses always take one of two shapes: { ok: {...} } or { err: { reason: string } }. Both are HTTP 200; only infrastructure errors (unknown slug, malformed JSON) return non-200.

Registering with Talus (operator workflow):

# 1. Local dry-run — no chain effect
nexus tool validate off-chain --url https://arsenal.sumplus.xyz/api/tools/cetus

# 2. Batch registration (requires Sumplus on Talus allowlist)
nexus tool register offchain \
  --url https://arsenal.sumplus.xyz/api/tools \
  --batch \
  --collateral-coin <sui_coin_id>

Tool registration on Talus is currently allowlist-gated during the Nexus beta. Contact the Talus team to be added. Local validate dry-runs work without allowlist access.

Error Codes