I connected Dots to a trading API and tested a BTC trend rule

Follow this worked strategy

I connected Dots to the NexusTrade trading API and had it research BTC-USD and test a 50-day trend rule across the completed 2024 run. The agent operated this workflow through NexusTrade's MCP server; it did not build the integration. The rule returned 56.61% against SPY at 25.30% and BTC at 119.27%, with $1909.24 in recorded fees. This is a development test on examined dates. Judge frozen rules on dates you have not used yet.

Follow the full journey

Step 1 of 6

Connect Dots

Copy server URL

https://nexustrade.io/api/mcp

Connect OpenAI Dots in the intended environment

Create the NexusTrade custom MCP plugin on ChatGPT web if it is not already installed. Use endpoint https://nexustrade.io/api/mcp with OAuth and complete NexusTrade sign-in. Open your dot’s profile → Customize → Plugins, select NexusTrade and complete any requested connection.

What you should see

The result identifies Apple's company filing, filing date and source URL. The connection check makes no account changes.

Copy connection check for Dots

Inspect the request

Use NexusTrade’s sec_edgar tool with action list_filings, ticker AAPL and limit 1. Report the company, filing form, filing date and source URL from the result. Use only this public read. Do not access portfolios, ingest filings, create resources or make changes. If the tool is unavailable, say so.

Step 2 of 6

Research BTC-USD and its trading calendar

Inspect the spot pair, source timestamps and fee model. This strategy evaluates daily indicators while crypto prices also move on weekends.

What you should see

A dated brief names the instrument, original sources and assumptions that matter to this strategy.

Copy prompt for DotsOpen in Aurora →

Inspect the request

Research BTC-USD for this spot-only BTC 50-day trend example. Report the asset, quoted currency, spot versus derivative distinction, trading calendar and price-source timestamps. Use original market and instrument sources. Check exchange or broker pair support separately from the historical model.

Step 3 of 6

Preview the BTC 50-day trend rules

Keep the exact daily indicator thresholds and flat-position guard shown here. Allocate 95% of buying power on entry and close all held units when the exit fires.

Entry

Saved rule: Price > SMA(50, Day) AND position value = 0

Exit

Saved rule: Price <= SMA(50, Day) AND position value > 0

Allocation

Saved rule: 95% of buying power per entry; sell 100% of held units on exit

Pair

Saved rule: BTC-USD

What you should see

The preview resolves this specific pair, entry, exit and fractional spot sizing.

Copy prompt for DotsOpen in Aurora →

Inspect the request

Use build_portfolio to preview this exact BTC 50-day trend configuration. Show the entry, sizing, exits, valid and issues. After I approve the rules, use create_portfolio once to save a new draft, then read it back and retain its returned ID. Keep this candidate separate from published research portfolios. Stop before submitting a paid test or deploying. { "name": "Public SEO crypto example - BTC 50-day trend", "initialValue": 10000, "cash": 10000, "buyingPower": 10000, "strategies": [ { "name": "Enter BTC 50-day trend", "condition": { "type": "And", "conditions": [ { "type": "Base", "lhs": { "type": "Price", "targetAsset": { "type": "Cryptocurrency", "symbol": "BTC-USD", "name": "BTC-USD" } }, "comparison": "greaterThan", "rhs": { "type": "SimpleMovingAverage", "targetAsset": { "type": "Cryptocurrency", "symbol": "BTC-USD", "name": "BTC-USD" }, "window": { "length": 50, "interval": "Day" } } }, { "type": "Base", "lhs": { "type": "PositionValue", "targetAssets": [ { "type": "Cryptocurrency", "symbol": "BTC-USD", "name": "BTC-USD" } ] }, "comparison": "equal", "rhs": { "type": "Value", "value": 0 } } ] }, "action": { "type": "Buy", "targetAsset": { "type": "Cryptocurrency", "symbol": "BTC-USD", "name": "BTC-USD" }, "amount": { "type": "percent of buying power", "amount": 95 } }, "orderExecution": { "type": "Market" } }, { "name": "Exit BTC 50-day trend", "condition": { "type": "And", "conditions": [ { "type": "Base", "lhs": { "type": "Price", "targetAsset": { "type": "Cryptocurrency", "symbol": "BTC-USD", "name": "BTC-USD" } }, "comparison": "lessThanOrEqual", "rhs": { "type": "SimpleMovingAverage", "targetAsset": { "type": "Cryptocurrency", "symbol": "BTC-USD", "name": "BTC-USD" }, "window": { "length": 50, "interval": "Day" } } }, { "type": "Base", "lhs": { "type": "PositionValue", "targetAssets": [ { "type": "Cryptocurrency", "symbol": "BTC-USD", "name": "BTC-USD" } ] }, "comparison": "greaterThan", "rhs": { "type": "Value", "value": 0 } } ] }, "action": { "type": "Sell", "targetAsset": { "type": "Cryptocurrency", "symbol": "BTC-USD", "name": "BTC-USD" }, "amount": { "type": "percent of current positions", "amount": 100 } }, "orderExecution": { "type": "Market" } } ], "supportsFractionalShares": true, "supportsCrypto": true, "alertsEnabled": false, "dividendPolicy": "cash" }

BTC 50-day trend 2024-12-31, 21:00:00 UTC

15,660.69

SPY buy and hold 2024-12-31, 21:00:00 UTC

12,530.29

BTC buy and hold 2024-12-31, 21:00:00 UTC

21,926.92

BTC 50-day trendSPY buy and holdBTC buy and holdHistorical simulation

Step 4 of 6

Inspect the completed BTC-USD test

Read this strategy curve alongside the full-capital SPY and BTC comparisons. The 0.7% fee on each fill is part of the recorded result.

Backtest return

56.61%

Reported maximum drawdown

28.77%

Total recorded trading fees

$1909.24

Ending portfolio value

$15660.69

What you should see

The completed 2024 BTC 50-day trend simulation returned 56.61% with reported maximum drawdown 28.77%.

Copy prompt for DotsOpen in Aurora →

Inspect the request

Prepare a daily 2024-01-01 through 2024-12-31 backtest of my exact BTC 50-day trend draft with $10,000, fractional spot units and the saved allocation. Preserve the 0.7% crypto fee per traded notional on every fill. Show the request and estimated cost before submission. Inspect the same returned test ID, pair-specific entry and exit events, cash, position values and full-capital SPY/BTC comparisons.

Step 5 of 6

Observe BTC 50-day trend in paper trading

Observe the BTC-USD rule prospectively with fractional spot units. Keep its daily indicator window and 95% entry allocation while recording weekend evaluations.

Inspect before accepting an order

The BTC-USD signal, spot units, fee, cash balance, flat-position guard, daily evaluation schedule and weekend behavior.

What you should see

Your paper portfolio has its own ID, start date, schedule and dated history. These forward observations begin with your own run.

Copy prompt for DotsOpen in Aurora →

Inspect the request

Read back the reviewed BTC 50-day trend draft. Prepare a separate paper-only deployment with the same rules and $10,000 starting capital. Show the plan for approval. Retain the resulting paper ID and verify its deployment type, timing, pending simulated orders and actual history. Inspect: The BTC-USD signal, spot units, fee, cash balance, flat-position guard, daily evaluation schedule and weekend behavior. Keep the rules fixed and brokerage accounts unchanged.

Step 6 of 6

Review BTC 50-day trend for live deployment

Check the actual connection for this specific spot pair before preparing a live move. Review venue support, pair naming, minimum order size and its operating calendar.

Open the live deployment walkthrough →

Account and instrument review

BTC-USD spot support, fractional units, minimum order size, venue fees, weekend timing and exits; stop if the pair is unsupported.

What you should see

The review identifies the target account, supported instruments, rule changes and approval settings before confirmation.

Copy prompt for DotsOpen in Aurora →

Inspect the request

Prepare a live deployment review for my BTC 50-day trend paper portfolio. Read the actual account and broker capabilities, incoming rules and any existing rules that would be disabled. Check: BTC-USD spot support, fractional units, minimum order size, venue fees, weekend timing and exits; stop if the pair is unsupported. Show the plan and keep live trading unchanged until I explicitly confirm it. If an instrument or action is unsupported, report it and stop.

Follow the Dots session

This guide runs on NexusTrade's MCP server. Dots operated the trading workflow below, from connection to the live review. The agent's role here is operating the workflow through that server.

The table names the tool call, the approval checkpoint, and the artifact to keep at each stage. Placeholders such as a returned draft ID stand for values your own run returns. This page records no IDs from anyone else's run.

The recorded anchor is the completed 2024 test below. The strategy returned 56.61% against SPY at 25.30% and BTC at 119.27%, with $1909.24 in recorded fees.

Where Dots stops for approval

Each consequential action in this guide waits at an approval gate. The agent previews first and acts only after explicit approval.

The rules preview returns valid and issues before anything is saved. The agent resolves problems and re-previews instead of saving a candidate with open problems.

1. Approve the rules before the agent saves them

   The agent previews the configuration with build_portfolio and shows entry, sizing, exits, valid, and issues. It saves with create_portfolio only after approval and reads the returned draft back.

2. Approve the test cost before the agent submits once

   Historical tests are paid runs. The agent shows the exact request and estimated cost for approval before submitting once, then polls the same returned test ID until complete.

3. Approve the paper plan and verify it is paper

   The paper deployment is a separate portfolio with its own ID. The agent shows the plan for approval, verifies the deployment type, and leaves brokerage accounts unchanged.

4. Confirm the live move explicitly, or nothing moves

   The agent reads the actual account and broker capabilities first and keeps live trading unchanged until explicit confirmation. It reports an unsupported instrument or action and stops.

Inspect the captured BTC-USD measurements

Inspect the recorded trades

Inspect the original signal record

{
  "eventType": "BuySignal",
  "event": {
    "eventType": "BuySignal",
    "timestamp": "2024-10-11T13:30:00.000Z",
    "signals": [
      {
        "conditionName": "BTC-USD last price > 50 Day BTC-USD SMA and Position market value (BTC-USD) = Constant 0",
        "audit": {
          "type": "minimal",
          "results": {
            "0.0": {
              "isTrue": true,
              "lhsValue": 61420.7109375,
              "rhsValue": 60767.41453125,
              "lhsError": null,
              "rhsError": null,
              "comparison": "greaterThan"
            },
            "0.1": {
              "isTrue": true,
              "lhsValue": 0,
              "rhsValue": 0,
              "lhsError": null,
              "rhsError": null,
              "comparison": "equal"
            }
          },
          "failuresOnly": false
        },
        "isTrue": true,
        "actionName": "Buy",
        "actionMetadata": {
          "buyOrSell": {
            "targetAsset": {
              "name": "BTC-USD",
              "symbol": "BTC-USD",
              "type": "Cryptocurrency",
              "underlyingSymbol": null,
              "optionType": null,
              "expirationDate": null,
              "strikePrice": null,
              "multiplier": null
            },
            "allocation": {
              "type": "percent of buying power",
              "amount": 95
            },
            "price": 61420.7109375,
            "orderType": "Market Order"
          }
        },
        "orderExecution": {
          "type": "Market"
        }
      }
    ]
  },
  "timestamp": 1728653400000
}

Continue exploring