3Commas review
Execution infrastructure for an external strategy
Public-source review updated 7 October 2026. We did not buy these plans, enter private rooms or audit subscriber accounts. Product descriptions are source-supported; the decision tests below are our analysis. The performance snapshot retained in the publisher profile was not refreshed to this source-check date.
Routing is a different purchase from research
3Commas documents sending custom signals to a Signal Bot from an external server. Its JSON-format settings can carry changing trade parameters. That is an execution interface, not evidence that the incoming strategy is profitable. A reader who already has a researched signal source is evaluating order transport and controls; a reader without one still has to obtain or build the decision process.
Test the boundary between an alert and an order
Write a sandbox acceptance list before connecting capital: wrong symbol, duplicate event, old event, insufficient balance, unavailable market, rejected close and manual cancellation. These are proposed tests, not claims that this review ran them or that every plan supplies an identical safeguard. Retain the raw alert and exchange order identifier so a missing fill can be assigned to the right part of the workflow.
Size and permissions need their own review
Verify current support for your exchange, contract and order type using the plan and bot documentation. Check units carefully: a percentage, a quote-currency amount and a contract quantity are different inputs. Restrict API permissions to the minimum required, avoid sharing secrets in public logs and confirm how access can be revoked. A correct signal sent with the wrong unit can create the wrong exposure.
Buying decision
Shortlist this product for automation capability rather than a platform-wide win rate. Price the originating signal separately and review renewal terms at checkout. Neither the public documentation nor this review supplies an independently reconciled live performance series for the strategy you intend to connect.
Primary sources
Compare spot, perpetual and bot workflows · All provider reviews
Interpret each JSON unit before connecting a strategy
An interface can accept numbers while their economic meaning still depends on another field. The official custom-signal example includes amount type, leverage and order parameters. A price deviation, percentage allocation and contract quantity are not the same unit. Retain the exact API or bot format version and selected configuration. A parser accepting the payload is evidence of one technical step, not that the account exposure matches the publisher's intended size.
In an invented dry-run packet, an amount of 0.1 has no amount-type field. The result is unresolved input meaning, not permission to assume 0.1 tokens or ten percent. A second classroom message declares ten token units under an expressly fictional mapping; that can be interpreted at the specified layer, but the venue acceptance and fill remain unsupplied. Never reuse a public documentation payload with live authority merely because its numbers look small.
Require order-state reconciliation after a timeout
A sender may not know whether a request was acted on when an acknowledgement is unavailable. The review needs a documented policy and authoritative order-state evidence, not a blanket assumption that a retry is safe. Ask which identifier ties the source message to each downstream operation and which component owns duplicate prevention. These are proposed acceptance questions, not features this desk has independently tested in every plan.
The finished fictional test labels first delivery received, repeated delivery observed, accepted order linked and fill missing. A separate rejected close remains visible beside the open quantity. The product's successful entry demonstration cannot supply the missing exit response. The useful finding may be that an integration is not ready for a reader's intended workflow, even when its public transport mechanism is understandable.
Budget for the outside strategy as well as infrastructure
An automation licence is not the fee for every outside research source, market-data entitlement or venue operation. Preserve the chosen plan's current commitment and cancellation terms without attaching a platform-wide return to the purchase. A separate source subscription can continue after one software licence ends, and outstanding account operations require their own inspection. Disconnection, cancellation and position closure should never share one unsupported done label.
Shortlist this category when you already have a defined decision process and need to investigate controlled routing. Defer when instrument mapping, permission scope or recovery ownership cannot be explained. The official material establishes an interface; the dry-run case is editorial. We did not route orders, evaluate account security or validate the originating strategy. A useful review keeps those limits while giving the buyer concrete records to request rather than a fabricated product score.
Related research
Retained source references
References retain the original source trail; a link is not evidence that every private claim or account record was independently audited.