What makes LTP RapidX Config notable?

1.2K downloads. Trust evidence available

How should LTP RapidX Config 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 Config

Use when an agent needs to install or configure RapidX CLI/MCP access, set production LTP credentials, locate the agent workspace MCP config, review integration, discover tools, or run read-only self-checks.

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

1.2k

Updated

Oct 11, 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/11/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 11, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 11, 2026
Adoption signal: 1.2K downloadsadoption · observed Oct 11, 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-config

Install using `clawhub skill install s173s0dt05mxhb6rxrs383nhg587xdfv:ltp-rapidx-config` 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-config before using production credentials.

Contract: missing

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

Documentation

CLAWHUB

143,995 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: ltp-rapidx-config
version: 1.0.17
description: Use when an agent needs to install or configure RapidX CLI/MCP access, set production LTP credentials, locate the agent workspace MCP config, review integration, discover tools, or run read-only self-checks.
---

# RapidX Config

Use this skill for setup and integration review only. Use `ltp-rapidx-trading` for portfolio, market, order, position, algo, and live trading workflows.

## Scope

- Configure the published RapidX CLI package as the single runtime entrypoint.
- Configure MCP by launching `rapidx mcp serve` from the agent's own workspace MCP config.
- Classify whether this agent host is `MCP_READY`, `CLI_ONLY_READY`, or `NOT_VERIFIED`.
- Verify real tool availability with read-only calls.
- Produce an integration review with masked credentials and actual evidence.

Do not describe how to install this skill inside the skill itself. Assume the skill has already been installed by the agent host.

## References

- Read `references/capability-overview.md` when checking expected CLI commands, MCP tools, capability names, or endpoint coverage.
- Read `references/best-practices.md` when doing a full RapidX Skills / CLI / MCP setup review or explaining the recommended external user flow.

## Workspace First

Before changing MCP config, identify the agent host workspace that will run RapidX:

1. State the active agent workspace path from session/runtime context.
2. Identify the workspace-local MCP config file read by this same agent host.
3. If the MCP config path is ambiguous, inspect the confirmed workspace for existing MCP settings.
4. If still ambiguous, ask the user which MCP config file this agent should edit.
5. Add or update `mcpServers.rapidx` only after the workspace and config path are known.

Never assume the source repository root, filesystem root, or a global home config is the right target.

## Credential Intake

Ask whether the user wants to provide credentials as a user-provided chat secret. This is the default path for non-programmers, but state the risk first: even protected chat-secret flows are controlled by the agent host and may be subject to that host's retention, access, or collaboration settings.

If the agent host has a dedicated chat-secret UI, ask the user to create three secrets with the exact names `LTP_ACCESS_KEY`, `LTP_SECRET_KEY`, and `LTP_API_HOST`. If the host has no chat-secret UI, ask whether the user wants the agent to write masked-reference placeholders into MCP config or whether they prefer to set local environment variables manually.

Offer alternatives when the user wants stronger isolation:

- Local shell environment variables.
- Enterprise or OS secret manager referenced by the MCP host.

Rules:

- Required variables are `LTP_ACCESS_KEY`, `LTP_SECRET_KEY`, and `LTP_API_HOST`.
- `LTP_API_HOST` has no default. Use the API host provided for the current environment.
- Do not use `LTP_BASE_URL`, `RAPIDX_BASE_URL`, or `RAPIDX_PORTFOLIO_*`.
- Do not ask f

_meta.json

{
  "ownerId": "kn73kps0f7zwmrka0kz101ymad87wexe",
  "slug": "ltp-rapidx-config",
  "version": "1.0.17",
  "publishedAt": 1788768863798
}

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:

Helps an agent install or configure RapidX CLI and MCP access, set production LTP credentials, locate workspace MCP configuration, review integration status, discover tools, and run read-only self-checks.

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

## Publisher:

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

### License/Terms of Use:

MIT-0

## Use Case:

Developers and operators use this skill to prepare an agent host for RapidX CLI or MCP workflows, configure required LTP credentials, verify tool discovery, and report whether the runtime is MCP_READY, CLI_ONLY_READY, or NOT_VERIFIED before trading workflows begin.

### Deployment Geography for Use:

Global

## Known Risks and Mitigations:

Risk: The skill can guide installation of a mutable trading CLI and configuration of production credentials for tools that may perform high-impact account actions.

Mitigation: Install only from trusted RapidX CLI package sources, prefer pinned workspace-local installs, and use least-privilege credentials where possible.

Risk: Persisting full production credentials in MCP configuration can expose sensitive trading access through host retention, collaboration, or local file access.

Mitigation: Prefer host-supported secret references or a secret manager, avoid writing production secrets directly into MCP config, and mask credentials in logs and reviews.

Risk: Live trading, cancel-all, leverage, and close-position actions can materially affect an account if executed without adequate confirmation.

Mitigation: Require explicit previews, user confirmations, runtime self-checks, and readbacks before any live trading or high-impact account action.

## Reference(s):

- [RapidX Capability Overview](references/capability-overview.md)
- [RapidX Skills / CLI / MCP Best Practices](references/best-practices.md)
- [LTP RapidX Config on ClawHub](https://clawhub.ai/liquiditytech/skills/ltp-rapidx-config)

## Skill Output:

**Output Type(s):** [guidance, shell commands, configuration, markdown]

**Output Format:** [Markdown with inline JSON and bash code blocks]

**Output Parameters:** [1D]

**Other Properties Related to Output:** [May include masked credential references, read-only self-check results, MCP readiness classification, and integration review findings.]

## 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.