# Crypto Trading Bots That Keep Their State Through the Night

> Crypto trading bots for exchange APIs and on-chain swaps, built to your strategy. Trade-only keys, rate limits, two-leg fills and a ledger you can reconcile.

Page: https://synapsereality.io/services/build/algorithmic-trading/crypto-trading-bots/
Last changed: 2026-11-16

## Scope

### This covers

Trading bots for crypto exchanges and on-chain swaps, built to a client's own strategy.

### This is not

Prediction market bots, which have their own page, or launching a token or an exchange, which we do not do.

### Measured by

Fills, fees and balances that reconcile with the exchange's own statements.

## Overview

A crypto trading bot runs against markets that never close. It has to keep its state through the
night, through an exchange's maintenance window and through its own restarts. The strategy is the part
you bring.

We build crypto bots to your strategy, on exchange APIs and on-chain. Market making, arbitrage
between venues, grid and DCA rules, entries and exits from your own models. You own the code, and the keys
stay in your accounts.

Prediction markets, sports exchanges and broker APIs are on the
[algorithmic trading page](https://synapsereality.io/services/build/algorithmic-trading/).

## What a crypto bot has to handle

**Keys that can trade and nothing else.** Exchanges give an API key its permissions one by one. On
Binance, a system-generated key with no IP restriction can only read, under the default security
settings. Withdrawal needs the key to be limited to trusted IP addresses in every case
([Binance](https://developers.binance.com/legacy-docs/wallet/account/api-key-permission)). The bot gets a key that trades from your server and cannot withdraw. If
that key is ever leaked, it can trade badly but it cannot empty the account.

**Rate limits.** Every exchange caps requests. Binance counts request weight per IP address and
orders per account. An address that keeps breaking the limits is banned automatically
([Binance API docs](https://github.com/binance/binance-spot-api-docs/blob/master/rest-api.md)).
The bots we build budget their requests and keep room for cancels, so a busy minute never blocks
the order that matters.

**Two venues, two clocks.** Arbitrage needs prices from both venues at the same instant, and fills
on both legs. When one leg fills and the other doesn't, the bot holds a position it never wanted.
It unwinds or hedges by a rule written before the bot ever traded.

**On-chain swaps.** A swap pays a network fee and fills at the pool's price when it lands. That
can differ from the price when it was sent. Every order carries a slippage limit and a deadline,
and the bot simulates the swap before it signs.

**Accounting.** Fees in one coin, fills in another, funding on perpetuals, transfers between
venues. The bot keeps a ledger you can reconcile with each exchange's statements.

All of the above was read on 16 November 2026.

## Who it is for

A trader, a fund or a crypto company with a strategy that has to run around the clock, on one exchange or across several.

## What you get

- The bot in your repository, connected to the exchanges and chains your strategy trades
- API keys that can trade and cannot withdraw, tied to your server's address where the exchange allows it
- A request budget per exchange, so the bot stays inside each venue's rate limits and keeps room to cancel
- A written rule for every half-filled trade across two venues, and the code that carries it out
- Slippage limits, deadlines and a simulation before every on-chain swap
- A ledger of fills, fees and funding that reconciles with each exchange's statements

## How it runs

1. Read the venues. Each exchange's API terms, rate limits and fees, what an API key is allowed to do, and whether your account's country may use it. On-chain, the pools and the network fees.
2. Write the rules and test them. Your strategy as rules, tested on trade and order book data with each venue's fees in. Arbitrage is tested with both legs, including the times one fails.
3. Build the bot. Market data, signals and orders per venue, with limits and the kill switch in their own layer, and every order recorded before it is sent.
4. Run it in stages. Paper trading on live prices, then a small live size with hard limits. Size goes up only when you approve the step.

## Questions

### Which exchanges can you build for?

Any exchange that offers an API for placing orders, and on-chain swaps on the chains your strategy needs. We read each venue's API terms and rate limits before we quote.

### Can the bot withdraw our funds?

Not if the exchange separates the permissions. On Binance, withdrawal can't be switched on until the key is limited to trusted IP addresses. We set up keys that can trade and nothing more.

### Do you build arbitrage and market-making bots?

Yes, both, to your rules. The hard part of both is the leg that does not fill. That rule is written before the bot trades, and it is tested.

### Can you build a copy-trading bot?

For your own account, yes. The bot follows the wallets or traders you choose and trades your account by your rules. Trading other people's accounts at your own discretion is portfolio management under Israeli law, and it needs a licence. We do not build that.

### Who owns the bot and the keys?

You own the code, the accounts and the keys. The keys live on servers you control, or on servers we run for you under a retainer, and never in the repository.

## Related services

- [Algorithmic Trading Software Development](https://synapsereality.io/services/build/algorithmic-trading/)
- [Prediction Market Bot Development](https://synapsereality.io/services/build/algorithmic-trading/prediction-market-bots/)
- [Backtest Audit](https://synapsereality.io/services/build/algorithmic-trading/backtest-audit/)
