Five research agents, one knowledge graph

Markets moveon storiesthat connect.

An experimental AI research platform for Indonesian stocks. Specialized agents study each stock's timeseries, sector rotation, money flow, narrative sentiment and market maker behavior, and join what they find to the news in one knowledge graph.

Access is by invitation. Message @jalankaki10k on X

Use cases

Not a screener.

A screener shows what moved. Momentum works out why, and keeps it where you and your own agent can ask.
scheduleafter the IDX closeTimeseries
  1. Read daily barsIDX market datadone
  2. Find patternstrends, breakouts, rangesdone
  3. Write to the grapheach pattern on its stockdone

Every pattern dated the day it formed.

Agent

Research agents

5 agents

Five agents study every listed stock after the close. Each reads its own part of the market and adds what it found to the graph, dated the day it held.

  1. BI board meetingraisesBI Ratesince 18 Jun 2025
  2. BI Ratelifts10Y SUN yieldsince 18 Jun 2025
  3. BI Rate cutalways helpsbank stocksended Jun 2025
  4. BI Rate cuthelps, while NIM holds,bank stockssince Jun 2025

The ended view is kept, with its reason. Drag the date to see the graph as it stood then.

Console

console.momentum.id

Search any stock, indicator or event and open its relations. Each one shows its direction, its source and the date it started to hold.

  • ClientClaude
  • As of2025-06-20
  • AboutBI Rate

Why did the IHSG slip that week?

  1. Find the momentum tools
  2. Search the graph as of the date
  3. Read the dated relations

An answer from dated relations, misreads left out.

From your agent

MCP

Connect Claude, Codex, Cursor or any MCP client. Your agent asks the graph and the agents' research directly, as it stood on any date.

Motion off

Numbers

Built from stories.

Story indexes
1M+
News, summaries and corrections, each dated when it happened.
Nodes
1K+
Events, indicators, companies and principles.
Edges
100K+
Relations with a direction and the date they started to hold.

The whole platform. The graph further down is a small sample of it, with names, facts and story texts masked for the public page.

Overview

A screener shows what moved.

Momentum keeps why.

Price, volume and ratios tell you what moved. They don't tell you why, or what moved with it.

The why lives in stories: a board meeting, a rate decision, foreign funds moving into bonds, a broker accumulating quietly.

Momentum's agents read the market every day and join what they find to those stories in one knowledge graph.

Every relation keeps its direction and the date it started to hold, so you can trace what moved what, and since when.

Your agentover MCP
knowledge graph5 agents · 2 sources
  1. IDX market datadaily, after the close
  2. Storiesnews · weekly summaries
  3. Timeseriesagent · daily bars
  4. Sector rotationagent · sector indices
  5. Money flowagent · broker summaries
  6. Market makeragent · broker tape
  7. Narrative sentimentagent · stories

Live graph

Click into the graph.

A small sample of momentum's real knowledge graph, with names, facts and story texts masked for the public page.
Knowledge graphMasked sample
Loading the knowledge graph…

How it works

It starts from stories, not tables.

Momentum's input is writing: weekly summaries, news, corrections. Follow one story from the text to the graph as you scroll.

  1. 1Ingest

    A story comes in.

    A weekly summary, a news item or a correction, dated when it happened, not when it was typed. The two dates are kept apart.

    Ingestadd_episode
    Weekly summaryhappened 18 Jun 2025typed 20 Jun 2025

    The BI board meeting raised the BI Rate. The 10Y SUN yield climbed as foreign flows moved into bonds, and the IHSG slipped.

    Happened
    18 Jun 2025
    what the graph is dated by
    Typed
    20 Jun 2025
    kept, never used as the date

    Queued for extraction

    Queued for extraction, dated when it happened.
    Motion off
  2. 2Extract

    Text becomes structure.

    Events, indicators and companies are taken from the text, with the relations between them and the direction of each.

    Extract5 nodes · 5 relations
    Weekly summaryhappened 18 Jun 2025typed 20 Jun 2025

    The BI board meeting raised the BI Rate. The 10Y SUN yield climbed as foreign flows moved into bonds, and the IHSG slipped.

    1. BI board meeting raises BI Ratepending review
    2. BI Rate lifts 10Y SUN yieldpending review
    3. 10Y SUN yield draws Foreign flowspending review
    4. BI Rate lifts IHSGpending review
    5. Foreign flows correlates with IHSGpending review
    Five nodes and five relations, all pending review.
  3. 3Review

    Nothing joins unchecked.

    Extractions wait in a review queue. Misreads are retracted, not deleted, so the history stays whole.

    Review queue4 approved · 1 retracted
    1. BI board meeting raises BI Rate approved
    2. BI Rate lifts 10Y SUN yield approved
    3. 10Y SUN yield draws Foreign flows approved
    4. BI Rate lifts IHSGmisread, retracted
    5. Foreign flows correlates with IHSG approved

    The retracted relation stays in the history, dashed. It never reaches the graph's answers.

    Four approved, one retracted. The misread stays, dashed.
  4. 4Trace

    Follow one event to the index.

    Every relation keeps its direction, so you can trace why: from an event, through each indicator it touched, to the index.

    Patheach relation dated 18 Jun 2025
    1. BI board meetingEventraises
    2. BI RateIndicatorlifts
    3. 10Y SUN yieldIndicatordraws
    4. Foreign flowsIndicatorcorrelates with
    5. IHSGIndicator
    One event to the index, each step with its direction and its date.
  5. 5Time

    Every view has a date.

    When a view turns out wrong, the old one isn't deleted: it's ended, with the reason. So you can see the view on any date, not just the latest.

    Views over timeBI Rate cuts and bank stocks

    Two views, one axis

    as of now
    1. Always good for banksended5 mo
    2. Good only while NIM holdsvalid16 mo

    As of now, the graph held

    “A BI Rate cut helps bank stocks only while net interest margins hold up”

    Corrected Jun 2025Reason kept: The effect on banks depended on their net interest margins.

    Today: the new view holds, and the old one is still there to read.
Ingestadd_episode
Weekly summaryhappened 18 Jun 2025typed 20 Jun 2025

The BI board meeting raised the BI Rate. The 10Y SUN yield climbed as foreign flows moved into bonds, and the IHSG slipped.

Happened
18 Jun 2025
what the graph is dated by
Typed
20 Jun 2025
kept, never used as the date

Queued for extraction

Queued for extraction, dated when it happened.
Motion off

Over MCP

Your agent, on the same graph.

Momentum has an MCP server. Claude, Codex, Cursor and other MCP clients query the graph and the agents' research directly, as it stood on any date.
Your MCP clientIHSG, week of 18 JuneDoneMotion off

Why did the IHSG slip in the week of 18 June 2025?

Found 3 momentum toolstools/list

  • search_brain
  • get_episode_result
  • get_pending_review
  1. search_brainIHSG slip · at 2025-06-20

    4 relations, each dated 18 Jun 2025

  2. search_brainBI Rate and the IHSG · at 2025-06-20

    1 misread, retracted in review

  3. get_episode_resultweekly summary, 18 Jun 2025

    The source story and its review

The BI board meeting raised the BI Rate on 18 June 2025. The 10Y SUN yield climbed, foreign flows moved into bonds, and the IHSG slipped with them. A direct link from the BI Rate to the IHSG was read from the same story but retracted in review, so it is left out.

Example session: the question “Why did the IHSG slip in the week of 18 June 2025?” lists momentum's MCP tools, calls search_brain twice as of 20 June 2025 and get_episode_result for the source story, and replies: The BI board meeting raised the BI Rate on 18 June 2025. The 10Y SUN yield climbed, foreign flows moved into bonds, and the IHSG slipped with them. A direct link from the BI Rate to the IHSG was read from the same story but retracted in review, so it is left out.

Answers come from dated relations, not from a model's memory. A misread retracted in review stays out of the answer, and the history stays whole. Sign in to the console for your MCP address and access token.

Get your MCP address

Questions

Questions.

Something else? Message @jalankaki10k on X.

See what moved what, and since when.

Open the console to trace the full graph, or connect your own agent over MCP.