domains / families / devops / axonx
axonx
authentic
Develop AxonX research plugins and operate quantitative research tasks through CLI or MCP, inspecting execution status, logs, artifacts, and lineage.
When to use
- Use when developing or modifying AxonX research plugins and their typed Task contracts.
- Use when a user requests AxonX research task submission, execution tracking, failure investigation, or artifact inspection.
- Use when integrating an external Agent with an existing AxonX MCP service.
When not to use
- Local Task execution supports Python 3.12+ on macOS/Linux; Windows is not a supported local runtime.
- An AxonX service and its configured credentials are required for HTTP/MCP operations. This file alone does not deploy a service.
- Research plugins, market data, and model configuration are separate dependencies. Example IDs and addresses are placeholders.
- The ETL code above is structural pseudocode and needs a real transform and complete output fields before execution.
- Backtest results do not establish future investment performance; compare costs and data assumptions before interpreting them.
- Source development requires an AxonX checkout; paths inside examples refer to that checkout or the selected service workspace as stated above.
Skill page
Source