Connect your agent online
The intended flow is sign in, choose an agent, approve its account scope and budget, then connect to KRYPTA’s hosted service. No local installation for users.
View hosted architecture
Open agent workspace KRYPTA / AGENT CONTROL CENTER
Let KRYPTA work within your rules. Or bring your own agent. One workspace for access, allocations and oversight.
Paper preview · No real deposits or live trading
KRYPTA AGENTThis page runs entirely in your browser. Paper units have no value. No wallet connection, custody, API credentials or real transactions are available.
01 / MANAGED AGENT
Configure an example mandate, review a sample decision and follow its paper receipt. Nothing leaves this page. This demo is separate from the Python research backend.
REVIEW BEFORE ACTIVATING
Define a paper allocation and review your limits. Each sample decision will show the policy checks before you apply it.
SAMPLE DECISION
The demo uses fixed fictional prices: ETH $2,500 and BTC $50,000. It does not forecast returns.
Pause discards the pending decision. Halt ends this mandate; neither action closes an existing paper position.
No mandate active. All demo state clears when you reload.
02 / CONNECT YOUR AGENT
KRYPTA is being built as a hosted service: use the website or connect your agent to an approved endpoint. End users will not need to run a local server. Hosted account access is not deployed yet.
HOSTED PRODUCT / CUSTOMER FLOW
The intended experience needs a website and an approved agent connection, not a server running on your computer. Customer access is not enabled yet.
Sign in on KRYPTA’s website. Customer account enrollment remains a launch requirement.
Choose the agent’s markets, account scope, budget and expiry. Keep revocation under owner control.
Use a managed agent or approved remote client. Review activity and permissions in the browser.
Only engineers testing the source need these commands. They do not start the hosted customer service.
Run from the reference checkout. The default process has no accounts, keys or trading authority.
Set the command to your Python environment, arguments to -m private_clob.mcp, and the working directory to the checkout.
Initialize, then list tools. Authenticated paper operations require a separately provisioned test session and local signing adapter.
python -m private_clob.mcpMinimal JSON-RPC stdio subset, not a certified full MCP implementation. This stdio tool is not the separate HTTP readiness service. No customer OAuth, wallet signing, deposits or withdrawals are enabled. Requests are plaintext on local stdio and in host memory.
Keep signing keys out of model prompts and client configuration shared with others. Never enter a seed phrase, private key or API secret on this page.
THE PATH TO REAL ASSETS
A production managed agent needs a separately reviewed funding and custody design, owner-controlled permissions, independent security review and reliable recovery. No return, privacy or loss limit is guaranteed by this prototype.
Verified deposit rails and an explicit custody model. No deposit address is available today.
Market and budget limits, expiry, signing isolation and account-wide emergency controls.
Durable state, full risk and liquidation systems, withdrawals and independent legal and security review.