

Understands full financial context
Payment patterns, portfolio composition, risk tolerance, tax constraints, jurisdictional limits — Clark supports the complete picture.
Clark is not a chatbot. It is a composable agentic runtime that orchestrates Krypton's full financial stack — running payroll, allocating vaults and settling cross-border payments, within the limits you set — and opens that stack to external AI agents over streamable MCP.
Everything Krypton Pay and the Yield Engine can do arrives at an agent as one endpoint. This handshake is live — run it and Krypton's own infrastructure answers.
curl -sN https://clark.kryptonfund.com/mcp \ -H 'Content-Type: application/json' \ -H 'Accept: application/json, text/event-stream' \ -d '{"jsonrpc":"2.0","id":1,"method":"initialize", "params":{"protocolVersion":"2024-11-05","capabilities":{}, "clientInfo":{"name":"you","version":"1.0"}}}'event: messagedata: {"jsonrpc":"2.0","id":1,"result":{ "protocolVersion":"2024-11-05", "serverInfo":{"name":"Krypton Strands HTTP MCP","version":"3.4.5"}}}Payments, portfolio, yield and tax are one surface to Clark, and it acts on natural language in real time — which is only safe because every action it takes is bounded by a mandate you wrote and, where it moves money, gated by an approval you give.
Four behaviours the runtime brings to every request it is handed — whether that request came from you, from a schedule, or from another agent over MCP.


Payment patterns, portfolio composition, risk tolerance, tax constraints, jurisdictional limits — Clark supports the complete picture.
Rebalances portfolios, routes surplus cash to Yield Engine, schedules cross-border payouts — without a single manual action from you.
External AI agents connect to Clark's full financial runtime. Every capability — Pay, Yield, Tax, Strategy — becomes an API for commerce.

Developers deploy custom financial agents. Earn per call, % AUM, or % yield. Network effects compound with every new agent added in place.
Fifteen seconds of the real app, running a question and then a payment without either one leaving the conversation. Pick a moment and the recording jumps to it.
Demo recording. Strategies, figures and handles on screen are illustrative. The send runs under a fully autonomous posture, with no approval gate in front of it.
Step 1 of 6: It opens on what it can do. The app's home screen showing four capability cards, with a Strategy & Backtesting panel opening onto a list of example requests.
Typical response time for most requests.
AI agent protocol.
Multiple languages supported.
The runtime exposes a query tool and an approval tool. That pairing is the whole safety model: an agent can propose anything, and nothing that moves money completes until a person clears the interrupt.
Routes a natural-language query through the remote Krypton orchestrator, across Pay and the Yield Engine.
Approves or rejects a pending interrupt before the run continues.
stops atkrypton-pay-approval
The endpoint is a streamable HTTP transport, so the handshake has a shape worth stating plainly rather than hiding behind a one-liner that would fail.
Returns the server's capabilities and an Mcp-Session-Id response header.
Echo the session id back as a request header. Every later call needs it.
Now the tool surface resolves. Responses stream as SSE, not plain JSON.
And what it resolves to is the two tools above. That is the whole surface.
Every agent call is tracked, metered and attributed. The registry ships with four agents covering the operations Krypton already runs.
Cross-border settlement and payroll. Called for anything that moves money between currencies.
Strategy routing across vaults. Called when idle capital has to be placed against a mandate.
QuantConnect Lean. Called to run a strategy over historical data before any capital is committed.
Jurisdiction-aware. Called to check what a proposed action means where the money actually lands.
Neither of these has shipped. They are on this page because a roadmap stated openly is worth more than a roadmap implied by silence.
Be told when each of these lands, rather than finding out from the changelog.
Krypton operates to the standards these authorisations require while the applications are in progress. Nothing below is granted yet, and this page says so in the same place it says everything else.
Cross-border payments
Strategy vaults
Krypton is not currently licensed as a payment institution or fund manager in any jurisdiction. The vaults are not registered products, no authorisation should be inferred from this page, and capital is at risk. What is live today, and what is not →
The MCP endpoint is live today. Point an agent at it, or join the waitlist for the Developer Platform.