MKT.TRADE expert pack for AI agents

Navigator does not place orders, manage an account, or connect to custody. docs

Load this before a structure pull. It covers the Navigator MCP tools whose descriptions were read on 2026-10-19. It does not send an order. After a human stamps a note, the order rules are the broker pack.

Where each note comes from:

• [docs] means a MKT.TRADE public page fetched on 2026-10-19, a Navigator tool description read that day, or a Navigator education search_faq result read that day. A public-page line links the page. A tool-description line says "tool description, 2026-10-19". A definition line names the faq id.
• [field] means a dated process lesson from an earlier session. What was seen. No story.
• A line with no tag is a desk rule. It is not vendor behavior.

This pack was not run against a sandbox. The public pages fetched on 2026-10-19 do not publish one. No line is an untagged test result.

Unofficial. The Agentic Trader pays for a MKT.TRADE subscription. This page is not a paid placement and not an endorsement. Not financial advice. No signals. Automated trading can lose money. If this pack is more than 30 days old, re-check the vendor's docs.

Last checked 2026-10-19. Re-check by 2026-11-18.

The pack is symbol-agnostic. Prompts and snippets use <SYMBOL>, <ASSET_CLASS>, and <EXCHANGE>. A block labeled "Worked example only" is the only place a named market appears. Prices in those blocks are arithmetic, not a live map and not a position.

How an expert works

1. The operator names the symbol, the asset class, and the venue. The agent does not pick a symbol. A missing field means no pull.
2. Research does not arm. A human stamps a note before any status can read armed. This pack does not send. The next order, if there is one, follows the TradeStation pack or the Alpaca pack.
3. Call Navigator on the MCP host. Omit timeframe and timeframes so the subscription stack returns. Set include_full_pricemap true when the full map is required, and present pricemap_raw.formatted_text. Do not paste raw JSON. Do not invent a level. Tool description, 2026-10-19.
4. Grade a level on a completed hourly close from the exchange that owns the symbol. The open bar is not used. The 05:00 bar is graded after 06:00 in that venue's timezone. Say which timezone.
5. Check the Daily period_date against that asset class's update time before any grade or alert. A prior-period Daily is not today's map.
6. One writer per lock file. A failed pull leaves the prior lock in place. Do not re-alert on the same period.
7. If it is not known, stop and ask. Never invent an endpoint, a field, a fill, or a rule.
8. Never print or ask for the API key. If one is pasted into the chat, tell the operator to revoke it and generate a new one from account settings. docs
9. The kill word is STOP. Cancel this session's working notes and end the session. This pack does not cancel broker orders. The broker pack does that.

Grading a completed hourly close

Kill and the fail tell use the close. A true hold needs the close on the held side of the shelf and the low on the held side of the shelf. A wick, a touch, or an intra-bar reclaim is traffic. It does not arm. An arm with no completed-hour receipt is void. Reason no_hourly_hold_receipt. Even with a true hold, if the live print is back through the shelf at stamp time, do not arm.

Navigator's last price and the exchange candle can differ. The exchange candle is the grade. If the hourly candle cannot be fetched, write NEED CANDLES and do not grade.

Fail tell. A completed hourly close under Daily DIR is information, not a package. While it is live, no long adds until a completed close is back at or above Daily DIR. The stricter line is at or above Daily DIR+AD.

AD-band kill. For a long that is armed, a completed hourly close below level minus AD disarms. AD is the AD on that level's timeframe from the current pull. Example arithmetic only. Level 100, AD 1.50, kill 98.50. A close at 99 is not the kill. For a short, the band is level plus AD. A close under the line but inside the band is a tell, not the kill. With nothing armed, a close through the kill price is a tell only. Stamp the kill within 5 minutes of the hourly close.

The CRX+ entry says that level has VAR bands only and "no AD band on this level." [docs] faq.level.crx_plus, read 2026-10-19. Do not invent an AD kill on a CRX+ level. If the payload has no AD for the code, write NO AD. Whether CRX- has no AD band is in Don't know: stop and ask.

Re-arm. After a real AD kill, a completed close back through level minus AD, then a completed close through the level, and the live print on the held side. When the prior exit was not an AD kill, one completed close at or above the level. The low is not required in that case. In both cases a human stamps. Research does not arm.

Receipt shape. Count every completed bar.

O/H/L/C/V
vs D DIR <level>. C <signed distance>. Daily fail tell.

"The first close under the line" is false if earlier completed hours already closed under it.

Worked example only. Coinbase Exchange public candles for BTC-USD. The candles operation on that page sets security to an empty list. The schema line is [timestamp, price_low, price_high, price_open, price_close]. The response items also list volume. Record volume when it is present. Do not require it. granularity must be 60, 300, 900, 3600, 21600, or 86400, or the request is rejected. One response holds at most 300 candles, or the request is rejected. Page the window. For any other symbol, use that venue's hourly candles. Do not point this URL at a stock. docs

https://api.exchange.coinbase.com/products/BTC-USD/candles?granularity=3600

First-hour traps

There is no install. The operator generates a key at app.mkt.trade, then adds the connector. docs

The setup page does not print a raw HTTP sample, a bearer header, or a REST path. Do not invent one.

Navigator_Setup actions are status and complete_onboarding, with accept_tos, enable_ffpp, and enable_trade_plan. Do not invent an onboarding URL. Tool description, 2026-10-19.

The setup page lists three checkboxes. Five-Factor Personality Profile, Prop Challenge, and Trade Mandate. docs Leave all three off for a structure-only pull. If a mandate is enabled and ACTIVE, mandate text follows the outlook. That text is not the level table. Tool description, 2026-10-19.

Other tools, and when to skip them.

• Navigator_Charts action chart_data. timeframe is a PriceMap period (daily, weekly, monthly, quarterly, yearly), not a 15-minute or 1-hour candle. compact defaults to true. Bar spacing is chosen on the server. The description's example is a daily period returning 5-minute bars. Those bars are a picture. The description does not mention period_date. Do not decide a roll from chart bars. Tool description, 2026-10-19.
• Navigator_Connect is read-only broker data. The tool description names four brokers, the same four as the broker-connect page. Actions are list_connections, account_summary, balances, positions, open_orders, and bars (CrossTrade or Schwab historical OHLC). It cannot place a trade or move funds. docs Tool description, 2026-10-19.
• Navigator_Options reads a Deribit and Derive collector database, not live APIs. exchange is deribit or derive, default deribit. It is not a listed US ETF option chain. Do not use it for a listed ETF option. The markets page says Navigator is connected to Deribit for live options context on BTC and ETH. Both sentences are in the product. See the stop list. Tool description, 2026-10-19. docs
• Navigator_Profile actions are get_profile and mandate_summary. Not a structure pull.

The demo is the two-week trial. docs

Clock trap. A shell that prints UTC is not the futures and equities clock. That clock is 5:30pm CST. The crypto clock is 00:20 UTC. docs

MCP vs API

The public setup path is the MCP host https://mcp.mkt.trade. docs

Use the MCP host for a supervised structure pull. The REST path, the header that carries the key, and whether the two paths return the same body are in Don't know: stop and ask.

Call shape

Trading path. Send symbol, asset_class, and exchange. Omit timeframe and timeframes for the full subscription stack. Frames outside the subscription are filtered. Tool description, 2026-10-19.

{"path":"trading","symbol":"<SYMBOL>","asset_class":"<ASSET_CLASS>","exchange":"<EXCHANGE>","include_full_pricemap":true}

One timeframe, when that is the question.

{"path":"trading","symbol":"<SYMBOL>","asset_class":"<ASSET_CLASS>","exchange":"<EXCHANGE>","timeframe":"daily"}

Education path, for a definition. Present the FAQ result. Do not rephrase it into a new rule. Tool description, 2026-10-19.

{"path":"education","action":"search_faq","query":"AD"}

State and playbook, when the question is the state and not the levels. Present doctrine.content or display_text verbatim. Daily state is MCS, weekly is POS, monthly is MPS. The same 26 MKT STATE tags. Tool description, 2026-10-19.

{"path":"education","action":"get_playbook","symbol":"<SYMBOL>","asset_class":"<ASSET_CLASS>","timeframe":"daily"}

asset_class defaults to CRYPTO. A stock pull that omits the class can be read as crypto. The enum is CASH, CRYPTO, ETF, FOREX, Futures, STOCK. strict_symbol_resolution true rejects a shorthand the server would expand into a full pair. Send the full symbol. Tool description, 2026-10-19.

exchange, when supplied, is strict and never falls back. When it is omitted, the tool text names two crypto symbols that default to one venue, and the same description says a full CRYPTO outlook uses Kraken. The education FAQ says "Crypto uses Kraken." Send the venue on every crypto pull so the note names the map. If exchange was omitted, stop. Do not pick a venue. Tool description, 2026-10-19. [docs] faq.supported_markets, read 2026-10-19.

Worked example only. The tool description lists Coinbase, Kraken, Binance, and Deribit. It says ETH can resolve to ETHUSD and BTC can resolve to BTCUSD. When exchange is omitted, BTCUSD and ETHUSD default to Coinbase for structure and OHLC.

Worked example only. Do not copy these three arguments onto another market.

{"path":"trading","symbol":"BTCUSD","asset_class":"CRYPTO","exchange":"Coinbase","include_full_pricemap":true}

external_ohlc is optional for FOREX, Futures, STOCK, CASH, and ETF, with at least 50 bars. Each bar needs timestamp, open, high, low, and close. Tool description, 2026-10-19.

Do not call list_instruments. The tool description says it was removed.

Order type and duration by session

Navigator does not place orders, so this section is not an order-type table. It is when each asset class's map goes live. docs A pull before the published update can still carry the prior Daily. Check period_date. [field]

The FAQ names futures and equity markets for 5:30pm CST, and crypto for 00:20 UTC. It does not name a FOREX minute. If the class is FOREX, stop and ask which clock the Daily uses. docs

[field] Crypto Daily lag, recorded by 2026-10-16. Across several sessions the new Daily period_date showed up between about 8:19 p.m. and 8:48 p.m. ET (00:19 UTC to 00:48 UTC). A pull at 8:00 p.m. ET carried the prior Daily. The window is an observation, not a cap.

[field] Weekly observation, recorded by 2026-10-16. A weekly period dated on the Sunday stayed in force through that week. Exact weekly, monthly, and quarterly roll minutes are not on the pages fetched. The yearly roll instant is not on those pages. Do not hard-code a January timestamp.

The PriceMap page says the map is set before the period opens and unchanged until it closes. docs The roll check uses period_date, not a price change. [field] 2026-10-09. If a later pull shows a different price on the same period_date, stop and ask. Do not overwrite the lock from a price change alone.

There is no intraday PriceMap in the tool's timeframe enum. The periods are daily, weekly, monthly, quarterly, and yearly. Tool description, 2026-10-19. The public product names those five. docs docs

Confirm gaps

A pull can succeed and still be the wrong map. Reject these. Do not treat a returned body as permission to grade.

previous_state accepts as_of, regime, risk_state, bias, active_setup, and focal_point. Tool description, 2026-10-19. Pass a prior row only when the operator asks for a delta. A delta section is not a new lock.

Don't double-send

• One writer per lock file. A second writer that renames the price field is a broken lock. [field] 2026-10-07.
• Do not re-alert on the same period. Alerts fired from a prior Daily were dropped. [field] 2026-10-16. Check period_date before an alert.
• A failed pull leaves the prior lock untouched. HTTP error, success false, a schema_version that is not the required one, missing timeframes, or a daily row with no period_date.
• A retry after a missed slot records the miss and pulls again. It does not append a second lock for the same period. [field] 2026-10-07.
• The tool schema read on 2026-10-19 has no client dedupe key and no version argument. Do not invent either.

Buy and sell table

This section does not apply. Navigator does not place orders, manage an account, or connect to custody. docs Every broker connection is read-only. Navigator can see balances, positions, and market data. It cannot place a trade or move funds. docs

The buy and sell names, the durations, and the confirm step live in the broker pack. Load AI agents for TradeStation or AI agents for Alpaca. Paste that order into Agent Order Check before it goes out.

A strategy alert is not an order. The alerts page shows three types. A1 fires when price enters the zone from VAR to AD (fade). A2 fires when price clears the AD boundary (breakout). A3 fires when price comes back through after A2 (reversal). docs Delivery on that page is Telegram, a REST polling endpoint with cursor pagination, and a signed webhook. The page labels OMS as architecture ready, pilot active. Do not turn that sentence into a send path.

A published example on that page, 2026-04-16 at 08:35 UTC, ETH/USD Daily, names the theme SELL DIR FADE, the trigger DIR, the initial target DP, the objective DT1, the regime R3 with the words Bullish Sentiment, and the state Neutral (NNT). The dollar prices on that page are a past alert. They are not a live quote and not a position.

Ticks and combos

Navigator does not publish a tick size or a combo order. This section is how a level is written.

Write every level to the cent. Prefix every level with Y, Q, M, W, or D, then the code. W DIR. D DP. A bare price is not a level. Any gap is named.

The intraday clock is the exchange hour. Navigator chart bars are a picture. Grade the exchange hour.

Read higher timeframes first. If two timeframes carry different theme names, write the split and keep both. The default pull omits timeframe so the subscription stack returns.

The market-timeframe page separates two layers. Market Timeframe is last period's footprint. Previous High, Midpoint, Close, and Low, and Open in one figure on that page. PriceMap is the structure. Critical Ranges, directional pivots, sentiment, breakout levels, targets, and risk boundaries. MarketColor is 26 signature states. Playbook is structure plus state, and the theme is Optimal, Hedge, or stand aside. docs Do not mix a prior-period high into a PriceMap code. If you cite the footprint, label it as the footprint.

Level codes

Do not infer the Critical Range from a ladder order. The tool description says the zone is UP to DP. CR+, CR-, CRX+, and CRX- are validation codes, not the zone name. Never abbreviate the zone as bare CR. Never use the deprecated label "DIR+CR". Use BUY or SELL DIR BREAKOUT. Tool description, 2026-10-19.

The same DIR bundle says the zone is UP to DP. The PriceMap page prints the Critical Range as UP, DIR, DP. docs The Critical Range FAQ writes the lower boundary as DP with a minus sign. [docs] faq.critical_range, read 2026-10-19. Write the code the payload uses. If both appear, stop. Do not pick one.

Look up a code with search_faq rather than guess. The tool names AD, VAR, APMD, DIR, UP, DP, CR+, CR-, UT/DT, and UL/DL. Tool description, 2026-10-19. The full ladder order was not in that description. Do not print an order that was not seen.

Theme names that appear on public pages include SELL DIR FADE, SELL UP REVERSAL, and the case of R aligned with UP, DIR, or DP. docs docs Those pages are evidence the names exist. They are not a position and not a result.

Flatten a row by the label the payload already uses. Do not recompute a band the payload already labels. If two labels differ, write the difference. Do not assert a field name that was not in the tool schema. The question of which field holds a derived label such as DIR+AD is in the stop list.

Look up a timeframe by its name, not by its position in the array.

def row(raw, name):
    frames = (raw.get("outlook") or {}).get("timeframes") or []
    for t in frames:
        if isinstance(t, dict) and str(t.get("timeframe", "")).lower() == name:
            return t
    return None

outlook.timeframes[] is the tool description. The function is a desk procedure.

If the operator uses the nine-line scorecard, they assign vendor codes to those rungs. A blank rung stays blank. Do not invent the assignment. A common assignment, which the operator can reject, is pivot = R, inner low = DP, inner high = UP, outer low = CRX-, outer high = CRX+, extension up = UT1, extension down = DT1. Invalidation is the AD-band kill on the line they name. The state label stays theirs. https://theagentictrader.com/skills/price-map-levels

Two-rung ladder

The two-rung ladder is the next two named levels above the print and the next two below, each at least 0.5% from the print and from the other rung, all prefixed. Name any skipped rung and the percent. Re-cut the ladder when the print moves and a rung falls inside 0.5%, and after every roll. Do not drop a cited rung. Do not add a CRX rung the note did not cite. [field] 2026-10-14 and 2026-10-16.

Hand the stack to the kill and hold check unchanged. https://theagentictrader.com/skills/kill-hold-rules

Underlying-to-proxy ratio

The pages fetched do not publish a ratio. Compute it when the map is on an underlying and the order would be in a proxy, such as a listed ETF.

ratio = proxy mid / underlying price, both prints from the same second. proxy level = underlying level x ratio.

Re-mark the ratio on every pull. Put both timestamps on the note. Do not carry a ratio into the next session. Whether fees or NAV move it is in the stop list.

A US ETF does not trade the crypto overnight. Grade an overnight underlying break on the proxy at the first executable proxy print. Options on the ETF follow the option session, not the underlying's 24-hour session. https://theagentictrader.com/skills/crypto-etf-options

Worked example only. Arithmetic, not a live quote and not a position. Underlying BTC-USD 81828.54, proxy IBIT 46.335, same second. Ratio = 46.335 / 81828.54 = 0.0005662 when rounded to 7 decimal places. An underlying level of 80000 maps to about 45.30 on the proxy. IBIT and FBTC are names in the ETF catalog returned by search_faq on 2026-10-19. The operator chooses the proxy. BTCUSD is the worked example, not the default symbol.

Packages

A package is a note, not an order. It names a timeframe-prefixed shelf, the trigger (a completed hourly close), the kill (level minus AD for that timeframe, or NO AD), the two rungs, and a status.

Status moves in this order. Soft-watch, then hold receipt, then qualifies, then armed only after a human stamp, then disarmed on the AD-band kill. Research does not arm. A quiet session files a null ticket. https://theagentictrader.com/skills/no-trade-ticket

Blocks. A chase in the middle of the range, an arm on a wick, an arm above the operator's written limit, and any arm with no completed-hourly receipt.

Do not invent a size. No unit count is on the public pages fetched 2026-10-19. The operator writes the limit. This pack does not send.

Weekly UP income is a recommended default, not a signal. While price is under Weekly UP and the plan uses margin, leave income mode closed. Raise the income question only when price is above Weekly UP, the weekly hedge theme on the payload is SELL UP REVERSAL, and the operator has set the mode to income. A short-call study at or above the Weekly UP proxy-equivalent is a hedge-financing check. It can be studied while income is closed. It still has to pass the covered-call rules, including that premium is not a return. https://theagentictrader.com/skills/options-income-rules

The next watch, if income is closed, is a reclaim of Weekly DIR and then Weekly UP. That is a sequence to observe. It is not an instruction to trade.

Reading status

Read these fields before you grade.

Two clocks

Every note has two times when a later pull exists.

• Structure as-of. The lock from the routine that ran after the map went live. This is the map you grade against until the next lock.
• Traffic as-of. A later pull in the same period. Traffic does not overwrite the lock.

Write both times, both period dates, the symbol, the asset class, and the venue.

def daily_period(raw):
    t = row(raw, "daily")
    if not t:
        return None, None
    return t.get("period_date"), t.get("as_of")

The check, before any grade or alert.

1. Name the Daily date you expect from that asset class's update time. If the clock has not passed, you still expect the prior Daily.
2. Read period_date on the daily row.
3. If that date is older than the date you expect, do not alert and do not grade against it.
4. A file-age check misses this. A one-day-old Daily can still look recent.
5. A price left over from an older map is stale. Do not use it. Rebuild the lock after the roll. [field] From 2026-10-09.
6. Navigator_Charts is not the roll check.

Failures

[field] 2026-10-16. A described payload was slimmer than the level array a client required. A client that requires the old level array would write an empty map. Keep the prior lock until a pull confirms the shape.

Going live

1. Research does not arm. The agent does not turn a note into an order.
2. A human stamps the note. Until that stamp, the status stays short of armed.
3. The broker pack takes the next step. TradeStation or Alpaca. That pack's checker runs before a send. Then Agent Order Check.
4. This pack has no simulator round trip because the vendor publishes no order sandbox and places no orders. Do not rehearse a send here.
5. A live-only reject from a broker is that broker pack's section, not this one.

Permissions

The pricing page, with one asset class selected (Crypto), printed these prices on 2026-10-19. The prices reflect that coverage. docs

The FAQ says Day Trader and Pro Trader each offer one class or all four. The classes are Crypto, Futures, Stocks/ETFs, and Forex. There is no two-class or three-class price. All-class dollar amounts are not on the pricing page. Stop and ask before you quote one.

Options are not a separate class. The FAQ says Day Trader includes Daily options analytics, Pro Trader includes Daily and Weekly, and Institutional includes Daily through Yearly. The pricing table prints a dash for Day Trader and Pro options analytics, and "Included" for Institutional. Both pages were fetched 2026-10-19. Stop and ask which sentence a given key follows.

Strategy alerts and chart integrations are included on all three columns of the pricing table. The trial converts unless cancelled. Class or tier can change, and billing is prorated. docs

The vendor is not a data provider and not an exchange. Live crypto data is included. For other markets, connect a broker, or pass external_ohlc when the class supports it. docs docs

Chart overlays, a picture of the same levels and not a second grade, are listed for NinjaTrader, Sierra Chart, TradeStation, TradingView, and Bookmap. The PriceMap page says Bookmap's setup guide is coming soon. The integrations page lists Bookmap and says the key works on any package, including the two-week trial. Auro Digital is the institutional indicator, with no client setup. docs docs If the operator needs Bookmap steps, stop.

The markets page says the same framework is on every listed market at all five timeframes. The pricing page says the timeframes you receive depend on the plan. The tool says frames outside the subscription are filtered. All three are in the product. Stop and ask which timeframes this key returns.

Symbols

Send <SYMBOL> as the vendor spells it. Refresh the list with path education, action search_faq, and query what markets are supported (or faq_id faq.supported_markets). Read supported_markets.asset_classes[]. Do not hard-code a list. Tool description, 2026-10-19.

Three counts were in view on 2026-10-19. They do not match.

Asset classes on the trading tool use the enum above, including mixed-case Futures. Crypto symbols in that FAQ are full pairs, not a bare base. Futures in that catalog are root codes such as ES.

Do not type an account id. This pack has none.

Unknown fields are rejected by the desk rule. Send only arguments that are on the tool schema read 2026-10-19.

Token and call costs

No token price and no numeric rate limit are on the pages fetched 2026-10-19.

One structure pass, on the path this pack uses, is one Navigator trading call for the stack, plus that venue's hourly candles for the grade. A definition is a separate education search_faq call. A chart is a separate Navigator_Charts call and is not the grade.

Education search limit defaults to 10. Tool description, 2026-10-19. That default is not a rate limit.

If success is false, do not wait a made-up number of seconds and retry in a loop. Keep the prior lock and stop. The rate-limit question, and whether a paged read counts against it, is in the stop list.

The trading tool description outranks a chart for the level table. Present pricemap_raw.formatted_text when the full map was requested. Do not invent levels from a picture.

Crash recovery

1. Keep the prior lock. A crash, a timeout, or a failed pull does not authorize a new file.
2. Read the lock that is already on disk. Match it by symbol, asset class, venue, and period_date.
3. An alert for a period that was already alerted is not sent again.
4. There is no client-tag field on the tool schema read 2026-10-19. Do not invent one. The lock file is the record.
5. [field] 2026-10-07. Hand-edited level files kept renaming the price field. One writer.

Order playbook

This is a pull-and-grade playbook. It does not place an order.

1. Ask for <SYMBOL>, <ASSET_CLASS>, and <EXCHANGE>. Do not pick a symbol.
2. Confirm Navigator is connected and name the tools you see. The 2026-10-19 list is in First-hour traps.
3. Read the clock. Name the asset class's update time from the table above. If the clock has not passed, expect the prior Daily.
4. Pull the full stack. Omit timeframe. Set include_full_pricemap true. Send the venue.
5. Read success, schema_version, and the daily period_date and as_of. If any gate in Confirm gaps or Failures fails, keep the prior lock and stop.
6. Write one receipt from a completed exchange hourly close. Name the candle source and the timezone.
7. Write one two-rung ladder from that pull. Prefix every level. Name any skipped rung.
8. If a proxy is in the note, re-mark the underlying-to-proxy ratio from the same second and put both timestamps on the note.
9. Stop. Research does not arm. A human stamps. Then the broker pack.

Checklist before the stamp.

• Structure as-of is the Daily you expect after that class's update time.
• Symbol, asset class, and venue are on the note. The symbol is the full symbol.
• Levels are prefixed and match the pull to the cent. Any gap is named.
• The trigger is a completed exchange hourly close. Not a wick. Not a forming bar.
• For a long, the live print is at or above the shelf at stamp time.
• The Daily fail tell is not live against a long add.
• The kill is level minus AD from this pull, for this timeframe, or the line says NO AD. The stamp is inside 5 minutes of the hour.
• Two rungs, each at least 0.5% apart, each cited.
• Nothing on the block list. The operator's limit allows it.
• Status is not armed unless a human stamped it.

Field lessons

Dates are when the miss was caught. No account, no size, no result.

• 2026-10-07. A scheduled pull did not run during a fast move. The routine records a missed slot and pulls again. [field]
• 2026-10-07. Hand-edited level files kept renaming the price field. One writer. A failed pull leaves the prior lock in place. [field]
• 2026-10-07. A quote parser stored the open and the mark froze. Name the field you grade. Grade the close. [field]
• 2026-10-08 and 2026-10-12. A kill was filed late. A Daily DIR alert was scored on the wrong map. [field]
• 2026-10-09. A roll check inferred the new Daily from chart level changes and was wrong. Use period_date. [field]
• From 2026-10-09. A kill price from an older weekly map stayed in a file and was still named a week later. Mark it stale. Do not use it. Rebuild after the roll. [field]
• 2026-10-13. A kill was stamped 14 minutes after the hourly close. The rule is five minutes. The close was a small distance under the line. Under the AD-band rule that close was not a kill. The miss was the clock and the rule. [field]
• 2026-10-13, evening. A forming bar was treated as a completed close. That read was void. [field]
• 2026-10-14. Daily rungs disappeared after the roll. Re-cut the two-rung ladder after every roll. [field]
• 2026-10-14. Price wicked through a downside pivot and the AD band and closed back above. That is a tag. It is not a hold and not a kill. [field]
• 2026-10-16. A ladder re-cut dropped a cited CR- rung and added a CRX- rung the note did not cite. Restore the cited rung. Do not add an uncited level. [field]
• 2026-10-16. A reader called one close under Daily DIR the first. Three completed hourly closes had already printed under that level inside nine hours. Count the completed bars. [field]
• 2026-10-16. Alerts fired from the prior Daily. They were dropped. Check the period date before you alert. [field]
• 2026-10-16. A described payload was slimmer than the level array a client required. Keep the prior lock until a pull confirms the shape. [field]
• Repeated, recorded by 2026-10-16. Grades were stamped 6 to 14 minutes past the hour. Grade in the first few minutes. The five-minute kill stamp depends on it. [field]

Don't know: stop and ask

Stop on these. Do not guess.

• How long is any version pin supported, what is the sunset date, and what is the notice period?
• Does a pinned body still contain schema_version 2.0.0, timeframes[], focal points, and the raw map?
• What schema_version does a trading outlook return today, and what is server_version on that body? Education search_faq on 2026-10-19 returned faq_search.v1.0.0 and server_version 2.1.0. The tool description says outlook schema_version 2.0.0.
• The tool schema read 2026-10-19 has no version argument. If a client needs an older shape, what field pins it?
• Does the server still accept the name AI_Navigator, or only Navigator?
• If level rows move to a paged section, what are the page size, the cursor, the order, and the snapshot lifetime, and does one call return all five timeframes?
• What does previous_state accept if the row shape changes?
• Do level math, rounding, and the crypto venue default stay the same across versions?
• Do codes stay the same, including AD variants, =R, and CRX?
• Are a short "holds" line and a "loses" line in a newer outlook drawn from published levels?
• What timezone is as_of, and does each timeframe row include its own period_date?
• Do MCP and REST return the same body, and what is the exact REST path? The setup page does not print one.
• Which header carries the API key on a call that is not the Claude connector form?
• What are the rate limits, and do paged reads count against them?
• The public pages do not publish a sandbox. Is there a sample structure pull the operator can point at?
• Where is the changelog, and where is the launch notice?
• Which timeframes does this key return? The pricing page, the markets page, and the live catalog disagree, and they disagree on symbol counts (507, 527, and 519).
• What are the all-class dollar prices? The pricing page showed one-class prices with Crypto selected ($99 and $249).
• Which options-analytics sentence wins, the pricing table dashes for Day Trader and Pro, or the FAQ lines (Daily on Day Trader, Daily and Weekly on Pro, Daily through Yearly on Institutional)?
• What is the exact weekly, monthly, and quarterly roll minute?
• Does the crypto Daily lag past 00:20 UTC have a cap?
• Is the yearly roll instant published?
• Is risk_state always on the row?
• Do stocks and ETFs return levels with no broker connected, or only a delayed price?
• When exchange is omitted, which sentence wins, the tool default named in the worked example under Call shape, or the FAQ line that crypto uses Kraken?
• Which Critical Range lower boundary does the payload use, DP or DP with a minus sign?
• Does CRX- have no AD band, on every symbol? The CRX+ entry says no AD band on CRX+.
• Does Navigator_Options have any role for a listed ETF option? The tool description says a Deribit and Derive collector database, not live APIs. The markets page says Navigator is connected to Deribit for live options context on BTC and ETH.
• How often should an underlying-to-proxy ratio be re-checked beyond every pull, and do fees or NAV move it?
• Does the vendor define a positive stack as daily R above weekly R above monthly R?
• Is there a commanding-timeframe field, and what is its name? It was not in the tool schema read 2026-10-19.
• What field name holds a derived label such as DIR+AD?
• Does Bookmap have a setup guide? The PriceMap page says it is coming soon. The integrations page lists Bookmap.
• What is the token lifetime, and what does one 401 mean? The setup page does not say.
• Which clock does a FOREX Daily use? The FAQ update sentence names futures, equities, and crypto.
• Can a level price change before the period closes? The PriceMap page says the map is unchanged until the period closes.
• What are the holiday and early-close times for the map clock? They are not on the pages fetched.

Look it up

One link per page. A plain curl that timed out is not a block. If a fetch fails, ask the operator to open the page.

• Navigator setup. Key, Claude connector, host https://mcp.mkt.trade. No REST sample on this page.
• Account. https://app.mkt.trade
• Pricing. One-class prices with Crypto selected, the tier table, 507 markets.
• PriceMap. Critical Range, R, the five timeframes, Bookmap setup coming soon.
• Markets. 527 markets, Deribit line, not a data provider.
• FAQ. What Navigator does not do, update times, futures month, plan classes, Founding 50.
• Market timeframe. Footprint versus PriceMap versus MarketColor. A plain curl returned HTTP 200 on 2026-10-19.
• Strategy alerts. A1, A2, A3, and one past alert's field names.
• TradeVision. Theme names, including SELL UP REVERSAL. Not a position.
• Integrations. Chart overlays. A plain curl timed out on 2026-10-19. The page text was read the same day. Ask the operator to open it if a later fetch fails.
• Broker connect. Read-only. The page names CrossTrade, two crypto brokers, and Charles Schwab. The crypto broker names are in the worked example under Call shape.
• Definitions that are not on those pages. Navigator education search_faq, read 2026-10-19. Faq ids faq.var_ad, faq.critical_range, faq.level.dir, faq.cr_interior_validation, faq.level.crx_plus, faq.level.r, faq.apmd, faq.supported_markets.
• Worked example only, candles. https://docs.cdp.coinbase.com/api-reference/exchange-api/rest-api/products/get-product-candles

Scorecards next to this pack, not a second map.

• https://theagentictrader.com/skills/price-map-levels
• https://theagentictrader.com/skills/multi-timeframe-levels
• https://theagentictrader.com/skills/kill-hold-rules