# Automation Examples

## Trading Bot Example Overview

This section collects open-source examples of trading bots and automation workflows built around VOOI Ultra: tools and Perps API.

The examples use API access available to registered VOOI Ultra users. VOOI Perps API is not available as a standalone public API.

{% hint style="warning" %}
These examples are provided for educational purposes only. They are not financial advice and do not guarantee profit.

The current bot examples were generated with AI-assisted development and tested before publication. They demonstrate how VOOI Ultra users can quickly prototype trading bots and agentic trading workflows using VOOI Perps API access available through VOOI Ultra.

Testing does not make the bots risk-free. Trading bots can place real orders and interact with real funds. Review the code, configuration, strategy, and risk controls before running any bot with live capital.
{% endhint %}

Each example focuses on a specific trading workflow, such as funding arbitrage, signal-based execution, indicator-based trading, or copy trading.

These examples show how VOOI Ultra users can explore agentic trading workflows, AI-assisted bot development, and prompt-driven customization of trading automation.

Treat the examples as starting points. You can run them, inspect the code, fork the repositories, or use an AI coding agent to help customize them for your own workflow.

## Before You Run an Example

Trading bot examples can place real orders and interact with real funds.

Before using any bot with live capital:

1. Choose an example and read the repository README.
2. Review how the strategy works, including requirements and risks.
3. Inspect the code yourself or ask an AI coding agent to review it.
4. Keep credentials private.
5. Run dry-run or test mode first, where available.
6. Start with small balances and conservative settings.
7. Monitor logs, open positions, and bot activity.
8. Make sure you understand how to stop the bot.

Move to live trading only after checking configuration, logs, and risk settings.

These examples are not financial advice and do not guarantee profit. They are technical examples for users who understand the risks of automated trading.

## Available examples

The collection of open-source trading bots will expand over time.

Currently available examples:

* **Funding Arbitrage Bot:** an open-source funding-rate arbitrage bot for delta-neutral cross-venue strategies.
* **Signal Bot:** an LLM-assisted Telegram signal trading bot that parses channel messages and routes valid signals to supported perpetual venues.

#### Future examples

More examples may be added over time, including:

1. Indicator-based trading
2. Copy trading
3. Portfolio automation
4. Custom strategy bots
5. Agent-assisted trading workflows

## Using AI coding agents

You can use AI coding agents such as Claude Code, Codex, or Cursor to inspect a bot repository, explain how the strategy works, review configuration files, and help adapt the bot to your workflow.

This can be useful for agentic trading and so-called vibe coding workflows: start from an existing open-source bot, describe what you want to change, and use an AI coding agent to help modify and test the implementation.

Live trading should only be enabled after reviewing the code, configuration, logs, and risk controls.

Detailed prompts and setup notes are included in the dedicated bot guides.

## Next steps

Check dedicated guides for:

* [Funding Arbitrage Bot Example](/vooi-ultra-v3/vooi_ultra-automationexamples/funding-arbitrage-bot-example.md)
* [Signal Bot Example](/vooi-ultra-v3/vooi_ultra-automationexamples/signal-bot-example.md)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.vooi.io/vooi-ultra-v3/vooi_ultra-automationexamples.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.