Guess what's coming? A small Loco SDK. An API. A read-only MCP connection. A huge next milestone for Studio Loco. 🚂 We’ve been building the tools to inspect liquidity, compare rebalance routes and preserve the evidence behind each decision. The next step is making that work accessible to other builders and AI assistants. The direction: • An SDK that makes Loco’s tooling easier to integrate into other applications. • An API for dashboards, analytics and external workflows. • A read-only MCP connection that lets compatible assistants inspect exposed data and help explain it. Imagine a developer bringing Loco’s liquidity analysis into their own terminal, or an assistant walking through an exported Flight Recorder record: the range, the strategy, the assumptions and the context behind a proposed move. That’s why this matters so much. Every integration creates another place where Loco can be useful. Builders can compose with the tools, bring their own interfaces and develop workflows we haven’t imagined yet. The read-only boundary is deliberate. Inspection and explanation can become easier while transaction approval stays explicit and under the user’s control. This is a major step toward making Studio Loco part of the infrastructure people build with across the Meteora ecosystem. Small integration surface. Much bigger possibilities. The train is opening new connections. 🚂

Studio Loco’s Rebalance Planner is live, and it’s now wired directly into Flight Recorder. 🚂 Take a real Meteora DLMM position and compare four routes: • Stay put. • Recenter at the same width. • Widen your chosen range. • Stage a move to another pool with the same token mints. The Planner reads fresh on-chain state and runs unsigned native rebalance simulations. You can inspect target bins, token amounts, SOL requirements and costs before rebuilding a review for wallet approval. Pool moves have two explicit stages: withdraw first, then prepare a fresh destination deposit using actual balances. Each stage requires approval, with later costs labelled as unpriced until reviewed. The Flight Recorder connection gives every comparison, option and selection a traceable history, linking through to subsequent reviews and wallet actions. The ranges, observed slot, strategy and assumptions stay attached to the decision. You can inspect that evidence and export it. Snapshots expire. Changed inputs invalidate reviews. Cost-recovery calculations use your own fee-income assumption. This is where we’re taking Loco: liquidity management with understandable decisions, explicit approvals and a history that LPs can learn from.