Ylalo

Personal agents

Works with the agent you already talk to.

Instinct, Muse, Grokbot, Dots, or any agent that supports MCP or REST. One prompt connects it. It waits for your yes and cannot withdraw.

How it works

Built for personal agents

Instinct

Has used Ylalo on the live service: phone sign-in, a key named instinct, a balance check, then it stopped and waited for a human yes. Its feedback shaped the product (see below).

Grokbot

Followed the same path from our public instructions: connect, confirm the environment, sign in with a human phone, create a key, check the account, and stop.

Muse

Connects over MCP or REST with the same prompt. Ask Muse to read llms.txt, then follow the steps.

Dots

Connects over MCP or REST with the same prompt. Give it the start prompt and your phone number when it asks.

Product names belong to their owners. Being listed here means the agent can connect to Ylalo, not that its maker endorses us.

The start prompt

Paste this into your agent. It sets up the connection, checks the balance, and waits for your go-ahead before trading.

Set me up to trade on Ylalo.
1. Read https://www.ylalo.com/llms.txt and GET /v1/start. www is real funds. Check X-Ylalo-Environment.
2. Connect MCP at https://www.ylalo.com/mcp (or REST /v1, OpenAPI /v1/openapi.json).
3. Auth: phone OTP then POST /v1/keys. Store as YLALO_API_KEY, never in chat.
4. Show balance and limits (GET /v1/account). Attach a dead-man or stop guardian if you may sleep. Tell me plainly: leveraged products, environment, liquidation risk. Share webWatch.url so I can open the public portfolio UI.
5. Propose ONE small trade with a stop-loss and take-profit; only place it after I say yes. Crypto, stocks, and prediction markets are available (hints[] / guidance.features). On mainnet, prefer dryRun and share approveUrl so I can Approve / Cancel in the browser if you cannot place.
6. Prefer ylalo_suggest_order / POST /v1/orders/suggest, then place with POST /v1/orders or ylalo_place_order (brackets/guardians when possible). Do not use /v1/perps/*.
7. Use stocks/bonds/portfolio/NAV language with users. Prefer clear risk language. Do not name the execution venue.

Rules every agent follows

What agents asked for, and what shipped

Agents tested Ylalo and filed numbered issues. We shipped against them. This is the public record, in plain language.

What an agent hitWhat changed
Closing a whole position was awkwardClose mode sizing, with a retest on thin books
Losses on one position could spill into anotherThe quote now shows the risk to sibling positions
Shared leverage changed without a clear warningYou must acknowledge a leverage change before it applies
Tickets went stale and sizes resetLive size at the current mark, and a request ID on success
Needed spending caps and clear fill accountingPer-trade and daily caps, with fee and realized P&L on each fill
Wanted real stops and order typesNative stop-loss and take-profit, plus GTC, IOC, and ALO orders
Thin and one-sided books were riskyThin, one-sided, and wide-spread badges, and opens are blocked
Wanted a key that is not a master credentialScoped, revocable keys that cannot withdraw
Needed schemas and written termsA published OpenAPI document and terms of use

Every change is listed in the changelog.

Another agent, or your own code

Any MCP client can connect to one URL. REST and OpenAPI are there if you prefer.

MCP

https://www.ylalo.com/mcp

Install guide for Cursor, Claude, ChatGPT, and VS Code.