What makes LTP RapidX Trading notable?

1.2K downloads. Trust evidence available

How should LTP RapidX Trading be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

LTP RapidX Trading

Use when an agent needs to operate RapidX through MCP or CLI for portfolio reads, market reads, order preview, order submit/replace/cancel, position management, algo orders, or explicit live trading verification.

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

1.2k

Updated

Oct 10, 2026

Version

1.0.17

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 1.2K downloads reported by the source. Last updated 10/10/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 10, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 10, 2026
Adoption signal: 1.2K downloadsadoption · observed Oct 10, 2026
Latest release: 1.0.17release · observed Sep 7, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s173s0dt05mxhb6rxrs383nhg587xdfv:ltp-rapidx-trading

Install using `clawhub skill install s173s0dt05mxhb6rxrs383nhg587xdfv:ltp-rapidx-trading` in an isolated environment before connecting it to live workloads.
No published capability contract is available yet, so validate auth and request/response behavior manually.
Review the upstream CLAWHUB listing at https://clawhub.ai/liquiditytech/ltp-rapidx-trading before using production credentials.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-liquiditytech-ltp-rapidx-trading/snapshot"

Documentation

CLAWHUB

144,000 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: ltp-rapidx-trading
version: 1.0.17
description: Use when an agent needs to operate RapidX through MCP or CLI for portfolio reads, market reads, order preview, order submit/replace/cancel, position management, algo orders, or explicit live trading verification.
---

# RapidX Trading

Use this skill after `ltp-rapidx-config` has confirmed the runtime path as `MCP_READY` or `CLI_ONLY_READY`. Prefer MCP tools only when the agent host is `MCP_READY`. Use direct CLI commands only when the confirmed path is `CLI_ONLY_READY`.

## References

- Read `references/capability-overview.md` when selecting a CLI command, MCP tool, capability id, or RapidX endpoint mapping.
- Read `references/best-practices.md` when planning a full workflow across skills, CLI, MCP, preview, automation, and readback.

## Non-Negotiable Rules

- Do not fake query or trading results. Every claim must come from an actual MCP tool or `rapidx ... --json` response, and final summaries must include `toolOrCommandEvidence` or equivalent observed evidence.
- Do not use shell bridge scripts, temporary JavaScript scripts, directory-changing shell chains, or chained shell invocations.
- Treat all trade-write tools as real production actions.
- Never submit a write without preview evidence and explicit user consent for that specific write, unless the user has explicitly enabled RapidX automation mode for the current scope in chat.
- Use `confirmation.submitToken` from the preview response as the submit `continueConsentId`.
- Keep business parameters unchanged between preview and submit. If symbol, side, positionSide, quantity, price, order id, leverage, or mode changes, create a new preview.
- If a write times out or the result is uncertain, query state before retrying.
- Never echo secrets.

## Invocation Path

Before any trading workflow, read the latest integration review from `ltp-rapidx-config` or run that skill first.

- `MCP_READY`: use `rapidx/...` MCP tools and do not shell out to wrapper scripts.
- `CLI_ONLY_READY`: use direct `rapidx ... --json` commands and do not claim MCP tools were called.
- `NOT_VERIFIED` or only `CLI_READY`: stop and run config self-check before portfolio, market, or trade workflows.

Do not switch paths during a task without new evidence. If an MCP call fails after `MCP_READY`, mark MCP degraded and verify state before retrying or falling back to CLI.

If MCP setup or discovery is missing, stale, or failing, stop trading setup work and return to `ltp-rapidx-config` MCP Config. Do not invent host-specific MCP add commands in this trading skill.

## Version Check

At the start of a trading session or before the first write in a session, check the cached release status once:

- `MCP_READY`: call `rapidx/update/check` once, then `rapidx/self-check`.
- `CLI_ONLY_READY`: run `rapidx update check --json`.

Do not perform a fresh network update check before every trade submit. If the update result is `WRITE_BLOCKED`, `UPGRADE_REQUIRED`, or `skillsUpdateReco

_meta.json

{
  "ownerId": "kn73kps0f7zwmrka0kz101ymad87wexe",
  "slug": "ltp-rapidx-trading",
  "version": "1.0.17",
  "publishedAt": 1788768887121
}

references/best-practices.md

# RapidX Skills / CLI / MCP Best Practices

## Overview

RapidX is delivered as a complete Agent integration stack:

- **Skills** teach the Agent how to install, configure, choose CLI or MCP, run self-checks, and operate RapidX.
- **CLI** is the unified local runtime for atomic operations and also starts the MCP server through `rapidx mcp serve`.
- **MCP** is the structured tool surface for MCP-capable Agents and shares the same CLI/Core capabilities.

The best practice is not to make users memorize every command. Let the Agent install and read the skills first. Load the installed `ltp-rapidx-config` skill to configure CLI/MCP and run self-checks, then load `ltp-rapidx-trading` for queries, preview, submit, automation, and readback. Skill names are not shell commands.

Recommended flow:

```text
Install Skills
→ ltp-rapidx-config installs/configures CLI
→ configure credentials and API host
→ choose MCP_READY or CLI_ONLY_READY
→ run self-check
→ ltp-rapidx-trading uses MCP or CLI
→ preview before write
→ submit
→ readback and reconcile
```

## 1. Role Of Each Layer

| Layer | Role | Best Practice |
|---|---|---|
| Skills | Agent guidance | Install and read `ltp-rapidx-config` first, then use `ltp-rapidx-trading`. |
| CLI | Unified local runtime | Install from official npm and use `rapidx ... --json` for CLI-only Agents. |
| MCP | Structured tool interface | Start with `rapidx mcp serve`; MCP-capable Agents call `rapidx/*` tools directly. |
| Core | Shared implementation | CLI and MCP share schemas, API client, preview, automation, audit, and self-check. |

The MCP server is not a separate package. It is started by the CLI:

```bash
rapidx mcp serve
```

MCP tools should call the shared RapidX core directly. They should not shell out through temporary scripts, wrapper files, or `cd ... && node ...` command chains.

## 2. Recommended External User Flow

### Step 1: Install Skills

Users can install skills themselves, or send an executable instruction to their Agent.

Recommended instruction to send to the Agent:

```text
You are my Agent. Install the RapidX skills into the current workspace using the skill installation method supported by your Agent host.

Source repository:
https://github.com/LiquidityTech/ltp-rapidx-skill

Install both skills:
- ltp-rapidx-config
- ltp-rapidx-trading

After installation, load and follow the installed `ltp-rapidx-config` skill first. It is not a shell command. Use it to install or upgrade @liquiditytech/rapidx-cli from official npm, configure RapidX credentials, configure MCP if this host supports MCP, and run RapidX self-check.

Do not start market queries or trading until you can report one of:
- MCP_READY
- CLI_ONLY_READY
- NOT_VERIFIED
```

The exact installation command depends on the Agent host. Use the official RapidX docs or skill repository README for Codex, Claude Code, Cursor, Gemini CLI, OpenCode, OpenClaw, and Hermes.

### Step 2: Use Config Skill

The Agent should load and follow `ltp-rapidx-config` b

references/capability-overview.md

# RapidX Capability Overview

Use `rapidx schema --json` or MCP `rapidx/tools` as the runtime source of truth. This reference is a compact map for Agent planning.

## Runtime Layers

| Layer | Purpose |
|---|---|
| CLI | Atomic local operations through `rapidx <domain> <action> --json` |
| MCP | Structured Agent tools served by `rapidx mcp serve` |
| Core | Shared schemas, credential resolution, RapidX API client, preview, automation, audit, and self-check |
| Skills | Agent guidance for setup, review, trading, automation, and readback |

## Diagnostics And Discovery

| CLI | MCP tool |
|---|---|
| `rapidx --version` | - |
| `rapidx schema --json` | `rapidx/tools` |
| `rapidx update check --json` | `rapidx/update/check` |
| `rapidx auth check` | - |
| `rapidx doctor --json` | - |
| `rapidx self-check --json` | `rapidx/self-check` |
| `rapidx mcp serve` | starts the MCP server |

## Automation

Automation sessions are local authorization sessions. They do not map to RapidX HTTP endpoints.

| CLI | MCP tool |
|---|---|
| `rapidx automation start` | `rapidx/automation/start` |
| `rapidx automation list` | `rapidx/automation/list` |
| `rapidx automation status` | `rapidx/automation/status` |
| `rapidx automation extend` | `rapidx/automation/extend` |
| `rapidx automation stop` | `rapidx/automation/stop` |

## Market

| CLI | MCP tool |
|---|---|
| `rapidx market get-ticker` | `rapidx/market/get-ticker` |
| `rapidx market get-orderbook` | `rapidx/market/get-orderbook` |
| `rapidx market get-klines` | `rapidx/market/get-klines` |
| `rapidx market get-funding-rate` | `rapidx/market/get-funding-rate` |
| `rapidx market get-mark-price` | `rapidx/market/get-mark-price` |
| `rapidx market get-symbol-info` | `rapidx/market/get-symbol-info` |
| `rapidx market get-open-interest` | `rapidx/market/get-open-interest` |

## Portfolio

| CLI | MCP tool | RapidX API |
|---|---|---|
| `rapidx portfolio overview` | `rapidx/portfolio/overview` | `GET /api/v1/trading/account` |
| `rapidx portfolio assets` | `rapidx/portfolio/assets` | `GET /api/v1/trading/portfolio/assets` |
| `rapidx portfolio statement` | `rapidx/portfolio/statement` | `GET /api/v1/trading/statement` |
| `rapidx portfolio user-fee-rate` | `rapidx/portfolio/user-fee-rate` | `GET /api/v1/broker/feeRate` |
| `rapidx portfolio position-bracket` | `rapidx/portfolio/position-bracket` | `GET /api/v1/trading/broker/positionBracket` |
| `rapidx portfolio set-position-mode` | `rapidx/portfolio/set-position-mode` | `POST /api/v1/trading/account` |

## Orders

| CLI | MCP tool | RapidX API |
|---|---|---|
| `rapidx order place-preview` | `rapidx/order/place-preview` | preview for place |
| `rapidx order replace-preview` | `rapidx/order/replace-preview` | preview for replace |
| `rapidx order cancel-preview` | `rapidx/order/cancel-preview` | preview for cancel |
| `rapidx order place` | `rapidx/order/place` | `POST /api/v1/trading/order` |
| `rapidx order replace` | `rapidx/order/replace` | `PUT /api/v1/trading/or

skill-card.md

## Description:

Use when an agent needs to operate RapidX through MCP or CLI for portfolio reads, market reads, order preview, order submit/replace/cancel, position management, algo orders, or explicit live trading verification.

This skill is ready for commercial/non-commercial use.

## Publisher:

[liquiditytech](https://clawhub.ai/user/liquiditytech)

### License/Terms of Use:

MIT-0

## Use Case:

External users, developers, and trading operators use this skill to guide an agent through RapidX portfolio reads, market reads, previewed order actions, position management, algo order workflows, automation sessions, and explicit live trading verification.

### Deployment Geography for Use:

Global

## Known Risks and Mitigations:

Risk: The skill can guide agents that have scoped access to live trading credentials and real trade-write authority.

Mitigation: Install only from a trusted RapidX CLI publisher, prefer a pinned and reviewed CLI version, use the host secret store, begin with read-only checks, and keep trading scope narrow.

Risk: Automation sessions can authorize multiple order lifecycle actions within the approved scope.

Mitigation: Enable automation only with explicit authorization for symbols, notional caps, duration, allowed actions, and allowed order types; use short sessions and stop automation when it is no longer needed.

## Reference(s):

- [RapidX Capability Overview](references/capability-overview.md)
- [RapidX Skills / CLI / MCP Best Practices](references/best-practices.md)

## Skill Output:

**Output Type(s):** [Guidance, Shell commands, API Calls, Configuration instructions]

**Output Format:** [Markdown guidance with inline command and tool examples]

**Output Parameters:** [1D]

**Other Properties Related to Output:** [Trade-write guidance requires preview evidence, explicit consent or scoped automation authorization, and readback before final claims.]

## Skill Version(s):

1.0.17 (source: frontmatter and server release evidence)

## Ethical Considerations:

Users should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.

Github ReposUpdated 1d agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.