running_trade
Read the IDX running trade tape print by print or grouped, filtered by ticker and buy/sell side, to inspect intraday trades from the session open.
Instructions
The running-trade tape: individual prints as they cross the exchange.
Omit symbol for the market-wide tape, pass it to follow one ticker. action filters to one side (BUY = buyer-initiated, SELL = seller-initiated); omitted means the endpoint's own default, which is not necessarily ALL.
grouped=true reads a different endpoint that returns the tape aggregated rather than print by print. It is not a display option: the two return different payloads.
WHICH SESSION AM I LOOKING AT. Both views carry data.date and it is the answer — read it rather than assuming today. Measured 2026-09-01 after the ~18:00 WIB broker release, both served that same day. Broker-derived and foreign-derived figures across this API publish at roughly 18:00 WIB, so before that release a payload carrying YESTERDAY's date is correct and not yet published — it is not stale data and not a bug. market_movers' foreign.isShown is the explicit flag for the same thing and flips false to true across that release.
INTRADAY BROKER ATTRIBUTION DOES NOT EXIST TO BE RETURNED. IDX closed broker codes on live running trade on 6 December 2021. So is_broker_exists: false with empty buyer/seller is an honest answer about the exchange, not a parse failure or a missing field — check that flag per row rather than concluding the projection broke.
THIS TAPE IS NOT LIVE. Measured against the live API during an open session, it runs about EIGHT TO TEN MINUTES BEHIND and refreshes in bursts — its head sat unchanged for over three minutes while the lag grew second for second, and the staleness is at Stockbit's origin, not in a CDN. Do not answer 'what just traded' from it. src/live/tape.ts exists because of this.
READ THIS BEFORE ASKING IT ABOUT THE CLOSE. Measured 2026-08-28: the window always starts at the SESSION OPEN, at most 100 rows come back however large limit is, and offset/page are accepted but move nothing. So on a busy ticker this tool can only ever show the first 100 prints of the day — the last trade before the close is NOT reachable through it at any argument. A limit above 100 is refused here rather than silently truncated. For the rest of the session use broker_flow_intraday, which covers 09:00 to 16:14 at one-minute resolution with per-broker value and volume — but note it serves the PREVIOUS session until the ~18:00 WIB broker release, so it does not answer 'what just traded' either. NOTHING here does; docs/LIVENESS.md is the one place that says what each source is worth and why.
order_by is required upstream and is NOT a time ordering: 1 is chronological from the open with real trade sizes, 2 and 3 both return lot-ascending rows that were every one a 1-lot trade when measured. None of the three returns the most recent prints and none returns the largest. 1 is the default because it is the only one that answers a question anyone asks.
An empty result is NORMAL outside 09:00-16:00 WIB — the tape is a live feed and nothing crosses when the market is shut. Call market_session before treating emptiness as a fault.
PENDING VERIFICATION: this response shape has not been observed live.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "running_trade"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max rows, 1-100. Larger is refused: the endpoint ignores it. | |
| action | No | ALL, BUY or SELL. Omitted sends no filter. | |
| symbol | No | IDX ticker. Omit for the market-wide tape. | |
| grouped | No | Read the aggregated view instead of the print-by-print tape. | |
| order_by | No | 1 chronological from the open (default), 2 and 3 lot-ascending. Not a time ordering. |