Source Hierarchy
Choosing A Surface
1
Name the host
Identify whether the user is in a coding-agent host, OpenClaw, a web LLM, CI, or application code.
2
Name the execution ability
Decide whether the environment can call tools, run shell commands, edit code, install a skill, read Markdown, or only answer from context.
3
Pick the narrowest surface
Use Markdown and OpenAPI for route decisions, CLI for terminal calls, MCP for tool-calling hosts, Skill for reusable procedures, and SDKs for application code. For REST, resolve the exact method and path in OpenAPI. For MCP, use only an advertised tool name and input schema; do not infer either from a REST route.
4
Add the data gate
Any generated backtest, alert, export, dashboard, or model job should include data-quality checks.
Agent Safety Rule
Do not call MCP, CLI, SDKs, OpenAPI, Markdown,llms.txt, or Skills “agents.” They are surfaces. Do not call OpenClaw a Skill or MCP server. It is a harness that can use those surfaces when configured. This distinction prevents setup docs from giving a user the wrong install path.
Stop And Ask When
The venue family is missing
The venue family is missing
Ask whether the user means Hyperliquid core, Hyperliquid Spot, HIP-3, HIP-4, or Lighter before generating a route.
The host cannot execute the selected surface
The host cannot execute the selected surface
Do not give MCP setup to a host that cannot call MCP tools, or Skill setup to a host that cannot load
SKILL.md workflows.The route is not in OpenAPI
The route is not in OpenAPI
Treat the request as outside the current public API contract until a public route exists.
The output feeds decisions
The output feeds decisions
Add data-quality status, coverage, latency, or incidents before the agent writes a backtest, alert, export, dashboard, or model job.
Next Step
Use Coding agents for host-level behavior, MCP server for MCP setup, Skill forSKILL.md workflows, and AI clients for prompt patterns.