AIKIT: correct exchange facts and bot code checks, while your AI builds the bot

When an AI writes a trading bot, it often guesses the tick size, the minimum order, the fees or the rate limits, and it forgets the stop-loss. AIKIT is a connector your AI can call in the middle of the build. It returns facts read from each venue's own pages and APIs, each with the source link, the date we read it and a signed receipt, and it checks the bot's code for common mistakes.

General information and code checks only, not financial advice. AIKIT does not give signals, does not say what to trade, and does not place orders. Test every bot on paper or testnet first.

What your AI gets

Tools and their cost in credits

Venues covered: OKX, Binance, Bybit, Kraken, Coinbase, Bitget, KuCoin, Gate, Interactive Brokers and MetaTrader 5 (broker spec pattern). Every reply carries the source, the date and a receipt id that you can check against our public key.

Beta. AIKIT is new. Coverage is growing, some gaps are listed below, and buying is not open yet.

What is covered, and what is coming soon

Coverage on 12 Nov 2026 (452 facts)

If AIKIT does not have a fact, it says so. It does not guess.

Where the facts come from

• We checked 28 possible sources. There is no single place with every exchange's rules, so each fact comes from the best source for that fact.
• The order we trust: the exchange's own live interface first, then its dated documentation. Other libraries and data vendors are used only to cross-check, never as the answer.
• For legal status (for example EU MiCA licences) the national regulator's register wins.
• If two equal sources disagree, we do not serve the fact.
• Every fact shows its source link, the date we read it and a signed receipt.

How it is different

• Exchange servers from OKX, Bybit, Kraken, Coinbase and others mainly place orders on their own venue. AIKIT covers many venues and answers the questions a bot gets wrong: size steps, minimums, fees, limits and error codes.
• Every fact comes with its official source and the date we read it. Most tools we looked at give neither.
• The code check looks for trading mistakes (size, stops, look-ahead, fees, error handling, keys, order loops, testnet or live), not just syntax.
• Prop firm rules come in the same connector, so a bot can be built to stay inside a challenge's limits.

Add it to your AI

First, download the one-file connector: tc_aikit_mcp.py (Python 3.8 or newer, no extra packages). If you leave the key empty, it gets a free trial key on its own. No sign-up is needed.

Claude Code

claude mcp add aikit -- python3 tc_aikit_mcp.py

Claude Desktop

Add this to claude_desktop_config.json, then restart the app:

{
  "mcpServers": {
    "aikit": {
      "command": "python3",
      "args": [
        "/path/to/tc_aikit_mcp.py"
      ],
      "env": {
        "AIKIT_KEY": "akt_your_key_or_leave_empty"
      }
    }
  }
}

Cursor and other clients that connect over HTTP

Add this to .cursor/mcp.json. Other clients that support remote MCP servers use the same URL and header:

{
  "mcpServers": {
    "aikit": {
      "url": "https://api.tradingcheckup.com/aikit/mcp",
      "headers": {
        "Authorization": "Bearer akt_your_key"
      }
    }
  }
}

ChatGPT

In a ChatGPT plan that allows custom connectors, add a connector with the server URL https://api.tradingcheckup.com/aikit/mcp and your key as a Bearer token.

Plain REST

curl -X POST https://api.tradingcheckup.com/v1/aikit/trial
curl -H "Authorization: Bearer akt_..." "https://api.tradingcheckup.com/v1/aikit/symbol?venue=okx&symbol=BTC-USDT"
curl -H "Authorization: Bearer akt_..." -d '{"code":"...","venue":"binance"}' https://api.tradingcheckup.com/v1/aikit/check

Pricing

Get the API on RapidAPI

Paid plans are sold on RapidAPI. The free beta key on this page (25 credits, no sign-up, one per network) keeps working for trying it out and for the MCP server.

Paid plans bill extra requests per call, as shown on the RapidAPI listing. Beta: no uptime promise yet. Facts and code checks only, not advice.

How we tested it

We set the pass marks before we saw any results, and we list the marks that were missed.

• Facts: 452 facts on 10 venues, each with its official source, the date read and a signed receipt (latest data update 12 Nov 2026). All receipts check out.
• Independent spot check (earlier set of 354 facts): a separate reviewer re-read 30 random facts on the official pages. 30 of 30 were correct.
• Second spot check (12 Nov 2026): a separate reviewer re-read 30 new random facts. 29 of 30 were correct; the one miss was a wrong unit label on an OKX market-order limit, which we fixed.
• Bot code check v3 (new), fresh sealed set of 47 bots written by others, scored once: it found 86.8% of the planted mistakes (pass mark 85%), 3.3% of its alerts were false (pass mark 10% or less), and 0 of 10 clean bots were flagged. The set had 47 bots, one fewer than the 48 we planned. MQL5 results were 100% found and 0% false on that set, which is small.
• Older sets: on the first set of 52 bots v3 found 97% with 1% false alerts, but that set was used while we built earlier versions. On the second set of 48 bots it found 91% but 38% of its alerts were false, so the check can still raise false alarms on bots unlike the fresh set. Treat results as a guide.
• Real AI test (earlier version, 15 sealed bot-building tasks): with AIKIT, the bots had 2 wrong exchange numbers, against 21 without it. Most of the gain was on an open model (gpt-oss-120b). Claude Haiku and Sonnet seldom guessed even without AIKIT, but with it they wrote in more of the real values.
• In 10 live calls through Claude, the AI chose the right tool in all 7 lookup questions without being told. For code review, it reviewed the code itself unless asked to use a checking tool, and then it used AIKIT every time. When credits ran out, it told the user and said where to buy more.
• After a clearer startup note (12 Nov 2026), Claude Haiku ran the code check in 10 of 10 fresh review requests. That is one model and 10 prompts, not proof for every AI.
• Speed on our server: median lookup 10 ms, median code check 20 ms (slowest 79 ms).

Docs

• GET /v1/aikit/venues is free and lists coverage.
• GET /v1/aikit/facts?venue=&topic=fees|limits|errors|symbols|testnet costs 1 credit.
• GET /v1/aikit/symbol?venue=&symbol=&market=spot|perp costs 1 credit.
• POST /v1/aikit/check with {code, filename, venue} costs 5 credits.
• GET /v1/aikit/prop?firm= costs 1 credit.
• GET /v1/aikit/balance, GET /v1/aikit/receipts/<id> and GET /v1/aikit/public-key are free.
• When credits run out, the API answers HTTP 402 with status: credits_used_up, credits_left, charged: 0 and buy_url.

Terms, privacy and refunds

• What it is: facts and code checks for information only. It is not financial advice, signals or a recommendation. You are responsible for your bot and your trades.
• Facts can change: venues change fees and rules. Each fact shows the date we read it. Confirm on the venue before you trade real money.
• Your code: it is checked in memory and is not stored. We log the key id, the tool, the credits used and the time. IP addresses are kept only as a one-way hash, to limit free trials.
• Refunds (when packs open): unused packs can be refunded within 14 days of purchase. The Developer plan can be cancelled at any time, and the current month stays active.
• Also see our terms, privacy policy, refund policy and disclaimer.