< 15 seconds
Typical response time for most requests.
Clark is being built to plan payroll, investments and cross-border payments, asking for your approval before money moves. It is designed to connect Krypton’s financial tools and give external AI agents access through MCP.
Clark is designed to bring Krypton Pay and the Yield Engine behind one interface: a single MCP endpoint for agents. The example shows the initialization request and an abridged response.
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"}}}Krypton Pay and the Yield Engine: the capabilities Clark is built to reach. Their money movement is planned, not live.
Clark is the orchestration layer between them: one runtime across both products.
One MCP interface for agents. The example request initializes a session; the response shown is abridged.
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.
Payment patterns, portfolio composition, risk tolerance, tax constraints and jurisdictional limits.
Run payroll for the full team — same as last month.
Twelve people, four currencies, each settling as a direct pair.
Illustrative example · planned capabilities
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.
Illustrative product preview
Payment patterns, portfolio composition, risk tolerance, tax constraints, jurisdictional limits. Clark supports the complete picture.

Illustrative product preview
Proposes rebalances, routes surplus cash toward the Yield Engine and schedules cross-border payouts. Anything that moves money waits for your approval.
Illustrative product preview
External AI agents connect to Clark's full financial runtime. Every capability (Pay, Yield, Tax, Strategy) becomes an API for commerce.
Illustrative product preview
On the roadmap: developers will be able to deploy custom financial agents and earn per call, a share of AUM or a share of yield.
The app, drawn rather than filmed: a request chosen out of what Clark can actually run, answered with its working attached, and then a payment made in the same thread. Pick a moment and it jumps there.
Hello @Rhea
ActiveBacktest Gold from 01/01/2025 to 09/09/2025 with 1000 USD
Processing…
The backtest for Gold from January 1 to September 9, 2025, using $1,000 of initial capital, shows a total return of 39.47%, a Sharpe ratio of 2.55, and a maximum drawdown of 6.95%. The historical price data for this period was retrieved successfully.
GOLD/USDT Price Chart
OHLC Candlestick Chart
Portfolio Performance
Portfolio value over time from 01/01/2025 to 09/09/2025
Portfolio Allocation
Final allocation percentages by asset
Asset Performance
Individual asset returns during backtest period
Send 100 AED to @Arjun
Clark opens from the wallet, not from a second app. And it opens on what it can actually run: the stack's jobs, one tap away in the bar you ask in, and behind them requests that execute rather than prompts to adapt.
The wallet, with Clark opened from it. The Ask Clark bar with its row of shortcuts, and a Strategy & Backtesting panel opening from the bar's more button onto example requests, one of which is copied.
01: One control from the balance
Typical response time for most requests.
AI agent protocol.
Multiple languages supported.
Clark exposes a query tool and an approval tool. The preview below shows the approval flow planned for a payment request: the agent asks, the run stops at an interrupt, and a person decides.
Interactive preview · approval behaviour planned
Routes a natural-language query through the remote Krypton orchestrator, across Pay and the Yield Engine.
Example: prepare a supplier payment
Approves or rejects a pending interrupt before the run continues.
stops atkrypton-pay-approval
After approval, the proposed run can continue.
Illustration only · no payment submitted
krypton_query routes a natural-language request through Clark, across Pay and the Yield Engine.
The endpoint is registered the way any MCP server is. Nothing here is Krypton-specific except the URL and who you say you are.
1{2 "mcpServers": {3 "clark": {4 "type": "http",5 "url": "https://clark.kryptonfund.com/mcp",6 "headers": {7 "X-Username": "krypton",8 "X-User-Id": "7895abe0-d992-488a-a848-e6b5bd0e300f"9 }10 }11 }12}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 is designed around four agents, covering the operations Krypton is being built to run.
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.
Developers deploy custom financial agents onto Clark's runtime, earning per call, per unit of AUM, or per unit of yield generated.
A registry where third-party agents are discovered, metered and monetised alongside the built-in set.
Explore Clark’s integration guide, or join the waitlist for the Developer Platform.