TRKR

Changelog

What we shipped

</and who asked for it>

TRKR is in beta, which means this list is the product roadmap running backwards. When a change comes from something a tester asked for, their name is on it — with their permission. If something here is wrong, missing, or annoying, the feedback button on every page is the fastest way to end up in a future entry.

  1. </open>Explore the data without an account

    The dataset pages and the playground are open to everyone. Read any asset, run a portfolio against every simulated future, and decide afterwards whether you want an account — which is now only for saving a strategy and downloading the dataset archive. The endpoints behind those pages gained rate limits at the same time, so an open door does not mean a slow one.

  2. </agents>A public page for connecting your own AI

    How to point Claude, ChatGPT or Antigravity at this data now lives on a page you can read without logging in, including the install command for each. The simulations stay here; the thinking happens in the assistant you already pay for.

  3. </links>Shared links arrive as a card, not a grey URL

    Every page carries a preview image and its own description, so a TRKR link posted in Slack, LinkedIn or a message renders as something worth clicking.

  4. </nav>The methodology is one click from anywhere

    How the engine builds a future — regimes, macro paths, and how it is scored against real history — was reachable only by direct link. It is in the top navigation now.

  5. </chatgpt>ChatGPT can connect to TRKR

    ChatGPT cannot send an API key to a data source, so the endpoint learned to sign you in instead. Add the connector, approve it here, and the tools appear — no key to copy.

  6. </antigravity>So can Google's Antigravity

    One command with your key, or none at all if you let it sign you in the way ChatGPT does.

  7. </scope>An approved assistant reaches the simulations, and nothing else

    Your saved strategies and your profile are out of reach for a connected app — enforced by the database itself rather than promised on a consent screen.

  8. </keys>One agent key at a time, retired in the right order

    Creating a key now retires the previous one first, so a key you have been told is dead cannot still be working somewhere.

  9. </beta>The beta opened

    The dataset explorer, the playground, accounts, and the feedback widget that decides what gets built next.

Tell us what to build next.

Every entry above started as someone using the thing and saying what was missing.

Join the beta